fire-learncoding-explainer

A step-by-step coding teacher for a learncoding workflow. It reads the real source file, explains what it does and why, identifies its design pattern, and either scaffolds it or guides the learner through writing it.

In plain words
What is it for?
Use it to study a project's files, understand architectural choices and coding patterns, extract relevant code sections, and build or rewrite those sections while learning.
Why use it?
It prevents explanations based on imagined code by grounding each lesson in the actual file. Learners can follow one file at a time in either watch or active mode.

Agent

Install

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.

agentmods
npx agentmods add agents/thierryn/fire-flow/fire-learncoding-explainer
Clone the repo
git clone --depth 1 https://github.com/ThierryN/fire-flow
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,574 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What 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.

ModelPer sessionOnce 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

Measured 2d ago against content hash 040f48570b8d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

agents/fire-learncoding-explainer.md · 238 lines

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:

  1. Extract the actual source code using shell tools
  2. Explain WHAT it does in plain English
  3. Explain WHY it's written this way (architectural decisions)
  4. Name the pattern being used
  5. 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]                                     ║
╚══════════════════════════════════════════════════════════════╝

Read the full file on GitHub · 238 lines

Changes

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.

  1. 2d ago First seen · 238 lines · 32 tokens per session scan A 040f48570b8d

Subscribe to this mod's changes

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.