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/navraj007in/architecture-cowork-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/commands/navraj007in/architecture-cowork-plugin/publish-api-docs)<a href="https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/publish-api-docs"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/publish-api-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/navraj007in/architecture-cowork-plugin/publish-api-docs"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/publish-api-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.00017 | $0.01285 |
| Opus 5 | $0.00009 | $0.00642 |
| Sonnet 5 | $0.00003 | $0.00257 |
| Haiku 4.5 | $0.00002 | $0.00128 |
Grade A, and why
publish-api-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 7d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/architect:publish-api-docs
Trigger
/architect:publish-api-docs
Purpose
After generating a blueprint with /architect:blueprint, this command takes the API artifacts (deliverable 4e — OpenAPI specs, AsyncAPI specs, Postman collections) and generates interactive, browsable API documentation. Output can be served locally, deployed to GitHub Pages, or used as static HTML files.
Workflow
Step 1: Check for API Artifacts
First, check architecture-output/_state.json. If it exists, read it in full — it provides instant access to project, tech_stack, components, design, entities, and personas without reading larger files. Use its values directly where available; fall back to SDL (check solution.sdl.yaml first; if absent, read sdl/README.md then the relevant module files) only for detail not in _state.json.
Check if a blueprint with API artifacts (deliverable 4e) exists earlier in the conversation.
If no blueprint or no API artifacts exist, respond:
"I need API specifications to publish. Run
/architect:blueprintfirst to generate your architecture with API artifacts, then come back here to create the documentation."
Step 2: Ask Configuration
Load skills/export-openapi/SKILL.md for the OpenAPI 3.1 export conventions this command follows when generating the raw spec files passed to the publisher agent.
Ask the user:
"How would you like the API docs?"
- Swagger UI + Redoc (default) — Both viewers for your REST API, plus raw spec files
- Swagger UI only — Just the interactive explorer
- Redoc only — Clean, readable documentation
"Where should I save them?"
- Default:
./api-docs/in the project directory"Want me to start a local preview server when done?" (yes/no)
Step 3: Delegate to API Docs Publisher Agent
Pass the following to the api-docs-publisher agent:
- All OpenAPI specs from deliverable 4e
- All AsyncAPI specs (if any)
- All Postman collections
- GraphQL schemas (if any)
- Output format preference
- Output directory
- Whether to start preview server
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.
- 7d ago First seen · 144 lines · 17 tokens per session scan A fdd4e58f713f
publish-api-docs is a command published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 1,285 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-09-03.
Other commands, from other repositories
document
On-demand documentation generation — API docs, architecture updates, user guides.
nyann:route-docs
Change documentation storage routing (local, Obsidian, Notion, or per-type split) and regenerate the doc scaffold to match.
codebase-knowledge
Present a structured knowledge document for this codebase — architecture overview, module map, public API surfaces, and patterns. Knowledge-presentation only (no defect ranking). Use /swe-workbench:audit-codebase for defect sweeps; /swe-workbench:document for generating new prose docs.
spec-docs
Generate user-facing documentation from spec and implementation.
docs
Generate or update OpenAPI spec from existing API routes.
better-auth:add-plugin
Add a better-auth plugin to an existing project. Configures server and client plugins with proper imports.