doc-checker

doc-checker is an agent for Claude Code from makigjuro/cloudstack-ai-plugins. It costs 20 tokens per session (639 once invoked), scanned A, original, MIT.

An advisory agent that checks whether documentation still matches code changes on the current branch. A branch is a separate line of development in a version-control system.

In plain words
What is it for?
Use it during pull-request preparation to check documentation related to API routes, data models, services, infrastructure, configuration, events, or frontend changes.
Why use it?
It highlights documentation that may be outdated before a pull request, without blocking the change.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the dev-workflow plugin — 14 skills, 4 agents, 2 hooks, 1 MCP server shipped together

Good fit Use it during pull-request preparation to check documentation related to API routes, data models, services, infrastructure, configuration, events, or frontend changes.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/makigjuro/cloudstack-ai-plugins/doc-checker
Install

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.

Clone the repo
git clone --depth 1 https://github.com/makigjuro/cloudstack-ai-plugins

Made for: Claude Code.

Or install dev-workflow, the plugin that ships this one along with the rest of its 14 skills, 4 agents, 2 hooks, 1 MCP server.

Wrote 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.

agentmods badge for doc-checker

README.md
[![agentmods](https://agentmods.dev/badge/agents/makigjuro/cloudstack-ai-plugins/doc-checker/github.svg)](https://agentmods.dev/agents/makigjuro/cloudstack-ai-plugins/doc-checker)
Your own site
<a href="https://agentmods.dev/agents/makigjuro/cloudstack-ai-plugins/doc-checker"><img src="https://agentmods.dev/badge/agents/makigjuro/cloudstack-ai-plugins/doc-checker/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.

agentmods 80×15 button for doc-checker

Your own site · 80×15
<a href="https://agentmods.dev/agents/makigjuro/cloudstack-ai-plugins/doc-checker"><img src="https://agentmods.dev/badge/agents/makigjuro/cloudstack-ai-plugins/doc-checker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 639 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00020 $0.00639
Opus 5.5 $0.00008 $0.00256
Sonnet 5.5 $0.00004 $0.00128
Haiku 4.5 $0.00002 $0.00064

Measured 1mo ago against content hash b58e72030c1b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

plugins/dev-workflow/agents/doc-checker.md · 87 lines

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:

  1. Read the doc
  2. Check if the new code is covered (endpoint routes, entity names, config keys)
  3. 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)

Read the full file on GitHub · 87 lines

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.

  1. 1mo ago First seen · 87 lines · 20 tokens per session scan A b58e72030c1b

Subscribe to this mod's changes

doc-checker is an agent published in the GitHub repository makigjuro/cloudstack-ai-plugins (1 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 639 once invoked, about $0.0001 per session on Opus 5.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.

Related

Other agents, from other repositories

ia-security-sentinel

Performs security audits for vulnerabilities, input validation, auth/authz, hardcoded secrets, and OWASP compliance. Use when reviewing code for security issues or before deployment.

iliaal/whetstone · 39 tokens

ia-database-guardian

Reviews database schema, constraints, and migration code for safety. Use when PRs touch migrations, data models, ID mappings, enum conversions, backfills, or persistent data. Postgres-specific query, index, and type patterns defer to the ia-postgresql skill; this agent is the migration-safety review gate.

iliaal/whetstone · 69 tokens

ia-deployment-verification-agent

Produces Go/No-Go deployment runbooks with SQL verification queries, rollback steps, and monitoring plans. Use after migration code is approved to build pre-check queries, watch commands, and rollback procedures for the deploy.

iliaal/whetstone · 49 tokens

ia-design-iterator

Iteratively refines UI design through N screenshot-analyze-improve cycles. Use PROACTIVELY when design changes aren't coming together after 1-2 attempts, or when user requests iterative refinement.

iliaal/whetstone · 45 tokens

ia-figma-design-sync

Compares web UI against Figma designs and reports discrepancies. Optionally implements fixes. Use for design fidelity review (Phase 1 only) or iterative design sync (Phase 1 + Phase 2).

iliaal/whetstone · 48 tokens

ia-pr-comment-resolver

Implements a single pre-agreed PR review comment: side-effect tracing, pattern compliance, and verification. Use when a comment's action is decided; not for judgment calls (use receiving-code-review skill) or bulk resolution (use /ia-resolve-pr command).

iliaal/whetstone · 59 tokens