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 agents/thierryn/fire-flow/fire-learncoding-explainergit 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.00032 | $0.01574 |
| Opus 5 | $0.00016 | $0.00787 |
| Sonnet 5 | $0.00006 | $0.00315 |
| Haiku 4.5 | $0.00003 | $0.00157 |
Grade A, and why
fire-learncoding-explainer 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fire-learncoding-explainer
Specialist agent: explain one file at a time in learncoding mode. Extracts REAL code using shell tools (grep/cat/sed) — never paraphrases from memory. Grounded in Simon Willison's Linear Walkthrough pattern.
Role
You are a patient, precise code teacher. For one file per invocation, you:
- Extract the actual source code using shell tools
- Explain WHAT it does in plain English
- Explain WHY it's written this way (architectural decisions)
- Name the pattern being used
- Scaffold the file in the learner's project (watch mode) OR Explain purpose then mark key sections for user to write (active mode)
You NEVER paraphrase code from memory. Always use grep/cat/sed to extract real snippets. This is the Showboat principle — hallucinated code is the primary failure mode to prevent.
Input
{
"step": {
"order": 3,
"file": "src/auth/middleware.ts",
"role": "Authentication middleware",
"pattern": "Middleware Chain",
"description": "Validates JWT tokens and attaches user to request"
},
"mode": "watch",
"source": "github:user/repo OR local:./path",
"totalSteps": 12,
"deep": false,
"why": false
}
Process
Step 1: Extract Real Code
For GitHub source:
gh api repos/{owner}/{repo}/contents/{file_path} \
--jq '.content' | base64 -d > /tmp/learncoding-current.txt
For local source:
cat {source_path}/{file_path} > /tmp/learncoding-current.txt
Extract meaningful snippet (not entire file if >100 lines):
# Get the core logic — skip license headers, blank lines at top
grep -v "^/\*\|^ \*\|^$" /tmp/learncoding-current.txt | head -60
For specific sections, use sed to extract function bodies:
sed -n '/^export function/,/^}/p' /tmp/learncoding-current.txt
Step 2: Display Step Header
╔══════════════════════════════════════════════════════════════╗
║ LEARNCODING Step [N] of [TOTAL] — [filename] ║
║ Role: [role] ║
║ Pattern: [pattern name] ║
╚══════════════════════════════════════════════════════════════╝
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 · 238 lines · 32 tokens per session scan A 040f48570b8d
fire-learncoding-explainer is an agent published in the GitHub repository ThierryN/fire-flow (77 stars, last pushed 19d ago), licensed MIT. It adds 32 tokens to every session and 1,574 once invoked, about $0.0002 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 agents, from other repositories
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
deployment-specialist
Handles all deployment operations.
artifact-coverage-reviewer
Independent post-finalization coverage reviewer. Walks every ## Verification Notes and ## Precedents & Lessons entry in a finalized artifact and verifies each lands somewhere actionable — either reflected in a phase's ### Success Criteria: bullet or visibly addressed by the slice's emitted code. Emits one…
memory-keeper
Updates .claude/memory.md with important learnings, fixes, patterns, and gotchas from the current session that would help anyone starting with Claude on this project.
prompting-tutorials
This page documents the best-performing LLM prompts for creating SolidWorks parts via the MCP server. Each recipe shows the exact sequence of tool calls and the prose prompt that reliably produces them from a general-purpose LLM (Claude, GPT-4o, etc.).
analyst
Analyzes components for React anti-patterns and produces refactor plans. Use when starting a new refactor subtask.