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/docs-generator)<a href="https://agentmods.dev/agents/navraj007in/architecture-cowork-plugin/docs-generator"><img src="https://agentmods.dev/badge/agents/navraj007in/architecture-cowork-plugin/docs-generator/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/docs-generator"><img src="https://agentmods.dev/badge/agents/navraj007in/architecture-cowork-plugin/docs-generator.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.00020 | $0.02563 |
| Opus 5 | $0.00010 | $0.01282 |
| Sonnet 5 | $0.00004 | $0.00513 |
| Haiku 4.5 | $0.00002 | $0.00256 |
Grade A, and why
docs-generator 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 12d 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.
curl https://api.example.com/health How it starts
The opening of the file, as written. The whole thing — 433 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Generator Agent
Autonomous documentation generation from project state, activity logs, and architecture decisions. Produces runbooks (deployment, rollback), architecture guides (C4 diagrams), ADRs (decision records), and incident playbooks.
Input
{
"modes": ["runbook", "architecture", "adr", "incident"],
"audience": "engineers",
"project": {
"name": "example-saas",
"stage": "growth"
},
"components": [
{ "name": "api-server", "type": "backend", "port": 3000, "deploy_target": "kubernetes" }
],
"activity_log": "architecture-output/_activity.jsonl"
}
Process
Mode 1: Runbooks
Generate operational runbooks for each component.
File: docs/runbooks/deploy-{component}.md
# Deploy {Component}
## Prerequisites
- [ ] Staging deployment successful
- [ ] All tests passing (see build results)
- [ ] Feature flags configured
- [ ] Database migrations reviewed
- [ ] Deployment window scheduled
## Steps
### 1. Pre-Deployment Checks
```bash
# Check service health
curl https://api.example.com/health
# Verify database connectivity
psql $DATABASE_URL -c "SELECT 1"
2. Create Release Branch
git checkout -b release/v0.2.0
git tag -a v0.2.0 -m "Release 0.2.0"
git push origin release/v0.2.0
3. Deploy to Staging
The CI/CD pipeline auto-deploys tagged releases. Monitor:
https://github.com/example/project/actions
4. Smoke Test on Staging
./scripts/smoke-test.sh https://staging-api.example.com
5. Deploy to Production
# AWS ECS
aws ecs update-service --cluster prod --service api-server \
--force-new-deployment
# Or Kubernetes
kubectl set image deployment/api-server \
api-server=registry.example.com/api-server:v0.2.0
# Monitor
kubectl logs -f deployment/api-server
6. Post-Deployment Verification
# Check pod/instance health
kubectl get pods -l app=api-server
# Run smoke tests
./scripts/smoke-test.sh https://api.example.com
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.
- 12d ago First seen · 433 lines · 20 tokens per session scan A 7f4d2014d067
docs-generator is an agent published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 20 tokens to every session and 2,563 once invoked, about $0.0001 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 agents, from other repositories
section-writer
Generates self-contained implementation section content. Outputs raw markdown. Used by /deep-plan for parallel section generation.
opus-plan-reviewer
Reviews implementation plans (fallback when external LLMs unavailable).
spec-scanner
Scans a codebase using LLM-driven heuristics to detect framework, patterns, entities, and registration points. Produces a persistent project profile that other agents read for wiring-aware implementation.
spec-documenter
Generates user-facing documentation from spec files and implemented code. Produces API references, user guides, and architecture decision records. Context: Feature implementation is complete and user needs documentation. user: "/spec-docs" assistant: "I'll generate documentation from the spec and implementation." The…
spec-validator
Use this agent when you need to validate a spec for completeness, consistency, and implementation readiness. Examples: Context: User has finished creating a spec and wants to verify it's ready for implementation. user: "I've finished the spec for user-authentication. Can you validate it?" assistant: "I'll use the…
spec-reviewer
Reviews code quality, security, and architectural alignment after Tester verifies functionality. Uses the reasoning tier for deep reasoning about subtle issues.