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/zevtos/agentpipeWrote 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/commands/zevtos/agentpipe/docs)<a href="https://agentmods.dev/commands/zevtos/agentpipe/docs"><img src="https://agentmods.dev/badge/commands/zevtos/agentpipe/docs/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/commands/zevtos/agentpipe/docs"><img src="https://agentmods.dev/badge/commands/zevtos/agentpipe/docs.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.00028 | $0.00765 |
| Opus 5.5 | $0.00011 | $0.00306 |
| Sonnet 5.5 | $0.00006 | $0.00153 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
docs 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 1mo 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are orchestrating documentation generation. Documentation must be accurate (verified against code), actionable (copy-pasteable commands), and maintainable.
Context
@CLAUDE.md
Doc Type
$ARGUMENTS
Pipeline
Step 1: Assess Current State
- Check what documentation already exists (README, docs/, doc/adr/, CHANGELOG, API docs)
- Check when docs were last updated vs when code was last changed
- Identify stale documentation (docs that reference code that has changed)
- Identify missing documentation (undocumented endpoints, modules without docs, missing runbooks)
Present: "Current documentation state: [summary]. Recommend updating: [list]."
Step 2: Generate/Update (Docs Agent)
Based on the doc type requested (or 'all' if not specified):
If 'api' or 'all':
Run the docs agent:
"Generate comprehensive API documentation.
Read all API endpoints in the codebase. For each endpoint document:
- HTTP method and path
- Description (what it does and when to use it)
- Request parameters, body schema with types and constraints
- Response schema with example response
- All error responses with codes and trigger conditions
- Authentication requirements
- Rate limiting behavior Verify every documented endpoint actually exists in code."
If 'readme' or 'all':
Run the docs agent:
"Update the project README.md.
Read the codebase to understand current state, then generate/update:
- Project description (one sentence)
- Quick start (3-5 steps that actually work — test them)
- Architecture overview
- Development setup (prerequisites, install, run, test)
- Deployment instructions
- Environment variables documentation
- Contributing guidelines"
If 'adr' or 'all':
Run the docs agent:
"Review the codebase for undocumented architectural decisions.
Look for: technology choices, patterns used, unusual configurations, commented explanations.
For each undocumented decision, generate an ADR in Nygard format.
Check existing ADRs in doc/adr/ or docs/adr/ — don't duplicate."
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.
- 1mo ago First seen · 96 lines · 0 tokens per session scan A 5c6e0eb9de4e
docs is a command published in the GitHub repository zevtos/agentpipe (11 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 765 once invoked, about $0.0001 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.