Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/thierryn/fire-flow/fire-learncodinggit clone --depth 1 https://github.com/ThierryN/fire-flowWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00028 | $0.02038 |
| Opus 5 | $0.00014 | $0.01019 |
| Sonnet 5 | $0.00006 | $0.00408 |
| Haiku 4.5 | $0.00003 | $0.00204 |
Grade A, and why
fire-learncoding scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fire-learncoding
Turn any codebase into a linear learning walkthrough. Anti-vibe-coding. Anti-cognitive-debt. Grounded in Simon Willison's Agentic Engineering Patterns (simonwillison.net/guides/agentic-engineering-patterns/)
The Philosophy
"If you don't understand the code, your only recourse is to ask AI to fix it for you — like paying off credit card debt with another credit card." — Simon Willison
This mode prevents cognitive debt by walking through every file from the entry point outward, explaining WHAT each piece does, WHY it's written that way, and WHICH pattern it uses. Real code is extracted via shell tools (grep, cat, sed) — never paraphrased from memory.
Arguments
arguments:
action:
required: false
type: string
options: [on, off, --from-github, --from-path]
description: "Toggle mode or load source"
--from-github:
type: string
description: "GitHub repo URL to learn from"
example: "/fire-learncoding --from-github https://github.com/user/repo"
--from-path:
type: string
description: "Local path to learn from"
example: "/fire-learncoding --from-path ./src"
--watch:
type: boolean
default: true
description: "Mode 1: Agent explains + scaffolds. You read and say 'next'."
--active:
type: boolean
default: false
description: "Mode 2: Agent explains purpose, you write the key logic."
--step:
type: integer
description: "Jump to a specific step (resume)"
example: "/fire-learncoding --step 5"
--entry:
type: string
description: "Override entry point detection"
example: "/fire-learncoding --entry src/server.ts"
Mode Reference
| Mode | Flag | You do | Agent does |
|---|---|---|---|
| Watch | --watch (default) |
Read + say "next" | Explains, scaffolds file |
| Active | --active |
Write key logic sections | Explains purpose, marks // WRITE THIS: |
| Hybrid | --hybrid (future) |
Fill in business logic TODOs | Scaffolds all boilerplate |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 243 lines · 28 tokens per session scan A ddd8e3614ab6
fire-learncoding is a command published in the GitHub repository ThierryN/fire-flow (77 stars, last pushed 19d ago), licensed MIT. It adds 28 tokens to every session and 2,038 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.