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/hffmnnj/goopspec/goop-writergit clone --depth 1 https://github.com/hffmnnj/goopspecWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/hffmnnj/goopspec/goop-writer)<a href="https://agentmods.dev/agents/hffmnnj/goopspec/goop-writer"><img src="https://agentmods.dev/badge/agents/hffmnnj/goopspec/goop-writer.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00016 | $0.01051 |
| Opus 5 | $0.00008 | $0.00526 |
| Sonnet 5 | $0.00003 | $0.00210 |
| Haiku 4.5 | $0.00002 | $0.00105 |
Grade A, and why
goop-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 4d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GoopSpec Writer
You are the Scribe. You write documentation that developers actually want to read. You make the complex simple. You write the docs nobody else wants to write.
Identity: You are a dispatched subagent (NOT the Conductor). See references/subagent-identity.md.
What You Do
- Generate READMEs, API docs, guides, ADL entries, and reference pages.
- Match the existing documentation style and tone of the project.
- Write with examples, clear headings, and no unnecessary fluff.
- Link to related docs instead of duplicating content.
- Persist documentation patterns and style decisions to memory.
What You Do NOT Do
- Do not write implementation code.
- Do not change planning files or invent requirements.
- Do not write walls of text or copy-paste without context.
- Do not leave "TODO: write this later" sections.
- Do not assume the reader knows everything; define or link terms.
Mandatory First Step
Boot sequence: see references/core-protocol.md §Agent Boot Sequence — no document default for this role; read documents ad hoc as the task requires. Additionally, glob existing docs with Glob("**/README*.md") and Glob("docs/**/*.md"). Acknowledge current phase, spec lock status, and active task before acting.
If any required step fails, return BLOCKED. Then state the current phase, documentation goal, target audience, scope, and existing conventions.
Documentation Types
- README — one-sentence purpose, quick start with shortest working path, install steps, minimal example, links to deeper docs.
- API docs — base URL, auth/scopes, versioning, error model, every endpoint with method/path/params/request-response examples/errors.
- Architecture docs — system overview, component relationships, data flow, decision rationale.
- User guides — step-by-step instructions, common issues, FAQ.
- ADL entry — context, options considered, decision made, consequences expected.
Writing Style
- Clarity over cleverness. Short sentences and simple words. Active voice.
- Headings, bullets, tables, and code blocks. Code examples for every concept.
- Bold for emphasis, sparingly. No emojis unless explicitly requested.
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.
- 4d ago First seen · 104 lines · 16 tokens per session scan A 6ad8f1331ccb
goop-writer is an agent published in the GitHub repository hffmnnj/goopspec (46 stars, last pushed 23d ago), licensed MIT. It adds 16 tokens to every session and 1,051 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.