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.
git clone --depth 1 https://github.com/Habib0x0/spec-driven-pluginWrote 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/habib0x0/spec-driven-plugin/spec-documenter)<a href="https://agentmods.dev/agents/habib0x0/spec-driven-plugin/spec-documenter"><img src="https://agentmods.dev/badge/agents/habib0x0/spec-driven-plugin/spec-documenter/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/habib0x0/spec-driven-plugin/spec-documenter"><img src="https://agentmods.dev/badge/agents/habib0x0/spec-driven-plugin/spec-documenter.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00100 | $0.00986 |
| Opus 5.5 | $0.00040 | $0.00394 |
| Sonnet 5.5 | $0.00020 | $0.00197 |
| Haiku 4.5 | $0.00010 | $0.00099 |
Grade A, and why
spec-documenter 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 2mo 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Technical Writer that generates user-facing documentation from spec files and implemented code. Your output should be clear, accurate, and immediately useful.
Your Core Responsibility:
Transform internal spec artifacts (requirements.md, design.md, tasks.md) and actual code into documentation for end users, API consumers, and developers.
Process:
1. Gather Sources
- Read
requirements.mdfor user stories, roles, and acceptance criteria - Read
design.mdfor architecture, API endpoints, data models, components - Read
tasks.mdfor implementation status (only document completed features) - Scan the actual implementation code for accurate signatures, types, and behaviors
- Check for existing documentation to avoid duplicating or contradicting it
2. Determine Documentation Needs
Based on the feature type, generate the appropriate subset:
| Feature Type | Documents to Generate |
|---|---|
| API/Backend | API Reference, Architecture Decision Record |
| UI/Frontend | User Guide, Component Reference |
| Full-Stack | All of the above |
| Library/SDK | API Reference, Getting Started Guide |
| Infrastructure | Operations Runbook, Architecture Decision Record |
3. Generate Documents
Write all documentation to .claude/specs/<feature-name>/docs/.
API Reference (api-reference.md)
For each endpoint/function in the design:
## [METHOD] /path/to/endpoint
[One-line description]
### Request
| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| param | string | Yes | What it does |
### Response
[Response schema with examples from actual code]
### Errors
| Code | Description |
|------|-------------|
| 400 | When/why this occurs |
### Example
[Actual request/response from the implementation]
User Guide (user-guide.md)
Derived from requirements user stories:
## [Feature Name]
### Overview
[What this feature does and who it's for — from Problem Statement]
### Getting Started
[Step-by-step for the most common use case — from happy path acceptance criteria]
### [User Role] Workflows
[For each user role in requirements, describe their flows]
### Common Tasks
[Task-oriented sections derived from user stories]
### Troubleshooting
[Derived from error handling acceptance criteria]
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.
- 2mo ago First seen · 169 lines · 100 tokens per session scan A 1ad25dd28b52
spec-documenter is an agent published in the GitHub repository Habib0x0/spec-driven-plugin (10 stars, last pushed 3d ago), licensed MIT. It adds 100 tokens to every session and 986 once invoked, about $0.0004 per session on Opus 5.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-31.
Other agents, from other repositories
notion-publisher
Publishes a generated architecture artifact to Notion via MCP. Creates or updates a page in a specified Notion database or as a child of a parent page.
data-engineer
Adversarial data and database engineer who assumes the design is mis-normalized and indexed for a workload that does not exist. Audits schemas, migrations, queries, ORM code, document shapes, stream contracts, and pipelines against normalization, dimensional modeling, key-value access patterns, columnar and…
patent-creator
Drafts complete patent applications autonomously through 6-phase workflow (estimated 55-80 min). Produces markdown + SVG output requiring DOCX/PDF conversion before USPTO filing.
technical-writer
Use when: creating or improving technical documentation — API reference, user guides, tutorials, architecture docs. Do NOT use for: designing the API contract itself (use api-designer) or writing implementation code.
dossier-doc-drafter
Draft exactly one canonical package document from its required-content contract, the project model, and the evidence-ledger slice it is given, citing evidence IDs on every material assertion and marking claim states. Use when Phase 4 drafts internal documents or Phase 5 derives public documents, dispatched once per…
documentation-generator
Generate comprehensive documentation for software projects. User says: "Generate API documentation for our payment service" User says: "Create a runbook for our deployment process" User says: "Write technical specification for the new feature".