One source of truth for agent rules · Challenge 05 · 中文版

Apply this to your repository

Checkpoint l0510 ptsself-reported — code from verify.pyAny coding agent (Claude Code 2.x / Codex CLI 0.x / Cursor)

One AGENTS.md, thin pointers everywhere else, and a failing check when it breaks.

Doing this with your agent? One sentence starts the whole course:

Read https://flypython.com/skills/flypython/SKILL.md and start the FlyPython course `agent-rules-single-source`.

Apply this to your repository

Objective

One AGENTS.md, thin pointers everywhere else, and a failing check when it breaks.

The lesson

In your own repository: write (or prune) AGENTS.md as the single rule source, replace every other rule file with a thin pointer, add rules_check.py and its test line to CI. The workflow is the product; the checker is just the guardrail.

Exercise

  • Run the checker from a clean checkout to prove it does not depend on your machine

Checkpoint

The lesson’s commands run, and you can answer these in your own words (the agent asks; you answer — that is the gate):

  1. Which command did this lesson run, and what did it decide?
  2. What failed at the start, and why — in your own words?
  3. Before trusting a similar change next time, what would you check first?

Expected evidence

The command transcript and your answers.

Hints

Stuck? Open one at a time.

Hint 1 — What this checkpoint tests

One AGENTS.md, thin pointers everywhere else, and a failing check when it breaks — applied to a repository you own.

Hint 2 — Keep pointers thin

Each pointer file: at most 10 non-empty lines and a reference to AGENTS.md. Rewrite, do not copy — copies drift.

Hint 3 — The honest record

Note which files you deleted or slimmed and what the checker cannot see (like rule *quality* — it checks consistency, not wisdom).

Submit

Done? Record it.

The 8-character code verify.py progress printed for this checkpoint — from the browser, or straight from your agent.

Youbrowser

Submit the claim code

Your agentauto-submit

Let the agent solve and submit

Hand it this checkpoint (copy button on hover) — it solves, verifies, and submits on its own:

Work on the FlyPython challenge "One source of truth for agent rules" (course id course-agent-rules), checkpoint l05.
Machine-readable brief: https://flypython.com/api/challenges/agent-rules-single-source
Open the course folder and read TASK.md first — it is the contract.
Rules: smallest change, no new dependencies, never edit tests/ or solution/.
Check with python verify.py until its gates pass, then report each claim code to me.
Target: solve only checkpoint l05, and submit it as soon as it passes.

With a token from your agent page (env FLYPYTHON_TOKEN), it records the result directly:

curl -X POST https://flypython.com/api/claims \
  -H "Authorization: Bearer $FLYPYTHON_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"claims":[{"course":"agent-rules-single-source","checkpoint":"l05","code":"<8-char code>"}]}'

Or install the full FlyPython agent skill once and skip the paste.

Files

The starter and verifier

Solving runs on your machine — your agent fetches the course files itself via /api/challenges/agent-rules-single-source/files; you download nothing by hand. Prefer reading the source? Browse the folder on GitHub ↗