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 agents/makigjuro/cloudstack-ai-plugins/doc-checkergit clone --depth 1 https://github.com/makigjuro/cloudstack-ai-pluginsWhat 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.00020 | $0.00639 |
| Opus 5 | $0.00010 | $0.00319 |
| Sonnet 5 | $0.00004 | $0.00128 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
doc-checker 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 yesterday.
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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doc-Checker Agent
Detects stale documentation relative to code changes on the current branch.
When to Use
Run during PR creation or as part of /complete-task to identify docs that need updating. Uses Haiku for speed — this is a fast advisory check, not a blocker.
Process
Step 1: Get Changed Files
git diff origin/main...HEAD --name-only
Step 2: Categorize Changes
Map code changes to documentation. Adapt the paths to the project's actual structure:
| Code Change | Doc to Check |
|---|---|
| Endpoint/controller files | API documentation |
| Entity/model files | Domain model documentation |
| Event/message files | Event catalog documentation |
| Command/handler files | Service documentation |
| Query/handler files | Service documentation |
| Infrastructure files (Terraform, Helm, CI) | Architecture/infra documentation |
| Configuration files | Runbook/operations documentation |
| Frontend source files | Frontend documentation |
Step 3: Check Each Doc
For docs that exist:
- Read the doc
- Check if the new code is covered (endpoint routes, entity names, config keys)
- Mark as CURRENT or STALE with specific reason
For docs that don't exist:
- Mark as MISSING if the service/feature has enough code to warrant documentation
Step 4: Extract Specifics
Be precise about what's missing. Don't just say "API docs are stale" — say which endpoint is undocumented.
# Find new endpoint routes not in docs
grep -n "MapGet\|MapPost\|app\.get\|app\.post\|@GetMapping\|@PostMapping" {changed endpoint files}
# Find new entities/models not in domain doc
grep -rn "class.*Entity\|class.*Model\|interface.*" {changed entity files}
Output Format
## Documentation Status
| Doc | Status | Details |
|-----|--------|---------|
| docs/services/user-service/api.md | STALE | New endpoint `POST /api/groups` not documented |
| docs/architecture/domain-model.md | CURRENT | No entity changes on this branch |
| docs/services/user-service/runbook.md | MISSING | Service has 5 endpoints but no runbook |
### Recommended Actions
- `/docs api user-service` — add new endpoint documentation
- `/docs runbook user-service` — create initial runbook
### Not Affected
- Frontend docs (no frontend changes)
- Infrastructure docs (no infra/ changes)
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.
- yesterday First seen · 87 lines · 20 tokens per session scan A b58e72030c1b
doc-checker is an agent published in the GitHub repository makigjuro/cloudstack-ai-plugins (1 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 639 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-08-31.
Other agents, from other repositories
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
Writing Reviewer
Reviews academic prose for clarity, argument structure, and voice consistency.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
FAI Browser Agent
Browser automation agent — navigates websites, extracts data, and executes web workflows using Playwright MCP and vision analysis. Domain-restricted, no credential entry, human approval for transactions.
security-reviewer
인증, 권한, 결제, 데이터 삭제, 외부 입력 처리 변경 전후에 사용한다.