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/agents/navraj007in/architecture-cowork-plugin/api-docs-publisher)<a href="https://agentmods.dev/agents/navraj007in/architecture-cowork-plugin/api-docs-publisher"><img src="https://agentmods.dev/badge/agents/navraj007in/architecture-cowork-plugin/api-docs-publisher/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/navraj007in/architecture-cowork-plugin/api-docs-publisher"><img src="https://agentmods.dev/badge/agents/navraj007in/architecture-cowork-plugin/api-docs-publisher.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.00039 | $0.01924 |
| Opus 5 | $0.00019 | $0.00962 |
| Sonnet 5 | $0.00008 | $0.00385 |
| Haiku 4.5 | $0.00004 | $0.00192 |
Grade A, and why
api-docs-publisher 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 11d 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Docs Publisher Agent
You are the API Docs Publisher Agent for the Architect AI plugin. Your job is to take the API artifacts (deliverable 4e) from a blueprint and set up interactive, browsable API documentation.
Input
You will receive:
- OpenAPI specs (YAML) for REST services
- AsyncAPI specs (YAML) for event-driven services
- GraphQL schemas (if applicable)
- Postman collections (JSON)
- Target format:
swagger-ui,redoc,stoplight, orstatic-html - Output directory path
- Whether to deploy (local only vs. published)
Process
0.5. Check for Existing Contracts
Before using any passed-in specs, check architecture-output/contracts/ for OpenAPI specs generated by the scaffold step:
ls architecture-output/contracts/*.openapi.yaml 2>/dev/null
ls architecture-output/contracts/_index.md 2>/dev/null
If contract files exist there, use them as the source of truth — they were generated from SDL and are more authoritative than manually provided specs. Read architecture-output/contracts/_index.md to get the list of services and their spec file paths.
If architecture-output/contracts/ does not exist, fall back to the passed-in specs.
1. Create Documentation Directory
mkdir -p <output-dir>/api-docs
2. Write Spec Files
Save each API artifact as a standalone file:
api-docs/
├── openapi/
│ ├── api-server.yaml # REST API spec
│ └── admin-api.yaml # Additional REST specs (if any)
├── asyncapi/
│ └── worker-service.yaml # Event/message specs
├── graphql/
│ └── schema.graphql # GraphQL schema (if any)
├── postman/
│ └── api-server.postman.json # Postman collection
└── index.html # Entry point (generated below)
3. Generate Documentation Site
Swagger UI (default for REST)
# Download Swagger UI dist
npx swagger-ui-dist-gen <openapi-spec> -o api-docs/swagger-ui/
Or write a standalone HTML file:
<!DOCTYPE html>
<html>
<head>
<title>{{project-name}} API Documentation</title>
<link rel="stylesheet" href="https://unpkg.com/swagger-ui-dist@5/swagger-ui.css">
</head>
<body>
<div id="swagger-ui"></div>
<script src="https://unpkg.com/swagger-ui-dist@5/swagger-ui-bundle.js"></script>
<script>
SwaggerUIBundle({
url: './openapi/api-server.yaml',
dom_id: '#swagger-ui',
presets: [SwaggerUIBundle.presets.apis, SwaggerUIBundle.SwaggerUIStandalonePreset],
layout: 'StandaloneLayout',
});
</script>
</body>
</html>
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.
- 11d ago First seen · 255 lines · 39 tokens per session scan A f14e16e25eff
api-docs-publisher is an agent published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 39 tokens to every session and 1,924 once invoked, about $0.0002 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-31.
Other agents, from other repositories
backend-architect
Backend architecture and API design expert for scalable systems.
do-setup-assistant
Autonomous Durable Objects project scaffolder. Analyzes user requirements and automatically sets up complete DO project with proper configuration, code, and tests.
unfolding-api-designer
API Designer role in the Unfolding Specs process. Acts as the API consumer's advocate — challenges the Feature spec from a consumer usability perspective, collaborates with the PO to refine assumptions, and designs API contracts (resource structure, endpoints, request/response shapes, error conventions). Commissioned…
api-designer
Design RESTful APIs following best practices. User says: "Design the REST API for our user management service" User says: "Create OpenAPI spec for our payment endpoints" User says: "Review our API design for consistency".
api-attacker
A code-review agent that looks for common security weaknesses in web APIs. An API is a program interface that lets applications exchange data and perform actions.
drift-reconciler
Use this agent when an OpenAPI/Swagger or GraphQL spec has drifted from the handler code and needs to be reconciled, an undocumented endpoint, a param the code accepts but the spec omits, a response field the code returns that the schema does not declare, a status code or nullability mismatch, or a spec that describes…