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 commands/cwoodruff/dotnet-claude-workshop-content/api-docsgit clone --depth 1 https://github.com/cwoodruff/dotnet-claude-workshop-contentWhat 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.00007 | $0.00207 |
| Opus 5 | $0.00003 | $0.00103 |
| Sonnet 5 | $0.00001 | $0.00041 |
| Haiku 4.5 | $0.00001 | $0.00021 |
Grade A, and why
api-docs scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Example**: one realistic curl invocation Copies of this mod
1 near-identical copy found in the catalogue:
- api-docs — 100% identical, 0 lines differ
What it actually says
Document the API surface for $ARGUMENTS (default: all endpoint groups in the Api project).
- Read Program.cs and every endpoint-mapping extension to enumerate routes — from source, not memory.
- For each endpoint produce:
VERB /route
- Purpose: one sentence
- Auth: required policy/role, or "anonymous"
- Request: body/route/query parameters with types and validation rules actually enforced in code
- Responses: each status code with its condition and response shape
- Example: one realistic curl invocation
- Order by resource, then by verb (GET, POST, PUT, PATCH, DELETE). Flag any endpoint whose implemented status codes deviate from the conventions in .claude/rules/aspnet-api.md.
Write the result to docs/api.md (create the folder if needed).
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 · 21 lines · 7 tokens per session scan A 1a3b93238d51
api-docs is a command published in the GitHub repository cwoodruff/dotnet-claude-workshop-content (2 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 207 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.