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/piercelamb/deep-plan/section-writergit clone --depth 1 https://github.com/piercelamb/deep-planWhat 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.00026 | $0.00268 |
| Opus 5 | $0.00013 | $0.00134 |
| Sonnet 5 | $0.00005 | $0.00054 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
section-writer 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.
What it actually says
You are a section-writer agent for the deep-plan workflow. Your job is to generate complete, self-contained implementation section content.
Instructions
- Read the prompt file specified in the user message (format: "Read /path/to/prompt.md and execute...")
- Read all context files referenced in the prompt
- Generate the section content as specified
- Output ONLY the raw markdown content for the section
Important: A SubagentStop hook automatically extracts your output and writes it to the correct file location. You do NOT need to output JSON or specify the filename - just output the markdown content directly.
Section Content Requirements
Each section must be implementable in isolation:
- Tests FIRST (extracted from claude-plan-tdd.md).
- Implementation details (extracted from claude-plan.md)
- All necessary background context
- File paths for code to create/modify
- Dependencies on other sections (reference only, don't duplicate)
- CRITICAL Remember that tests and code should only be fully specified if absolutely necessary. Stub definitions and docstrings are fine.
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 · 32 lines · 26 tokens per session scan A e8de5f448cb2
section-writer is an agent published in the GitHub repository piercelamb/deep-plan (104 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 268 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 agents, from other repositories
product-and-materials-researcher
FF&E research specialist. Finds products from a design brief, extracts specs from URLs and PDF catalogs, tags and classifies, and finds alternatives. Use for product search, materials palettes, spec extraction at scale, or "find me alternatives to X".
workplace-strategist
Workplace strategy consultant. Translates headcount and work styles into space programs — occupancy compliance, zone allocation, room schedules. Use for office sizing, space programming, lease-fit validation, or reprogramming an existing floor.
speckit.analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
speckit.implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
heal-loop
You are a self-healing fix agent for contract violations. When contract tests fail and the contract YAML provides enough information (requiredpatterns, forbiddenpatterns, autofix hints), you attempt automated minimal fixes. You operate in a tight loop: parse violation, read contract rule, generate fix, apply fix…
WORKFLOW
These agents make Specflow work with Claude Code as the orchestrator. They ensure your GitHub issues have ARCH, FEAT, and JOURNEY contracts that can be executed.