What is inspector-documentation?

A pre-release documentation inspector that compares the written documentation with the code. It also looks for undocumented public interfaces and missing explanations for non-obvious decisions.

Use it before delivery to check endpoints, exported code, models, configuration, architecture notes, README files, and rationale for unusual implementation choices.

It finds documentation that misleads future developers or leaves them to reconstruct how and why the software works.

inspector-documentation — Agent for coding agents by mumerfarooq-con: A pre-release documentation inspector that compares the written docume

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.

agentmods

npx agentmods add agents/mumerfarooq-con/asdlc-tools/inspector-documentation

Clone the repo

git clone --depth 1 https://github.com/mumerfarooq-con/asdlc-tools

Or install asdlc, the plugin that ships this one along with the rest of its 3 commands, 15 agents.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/mumerfarooq-con/asdlc-tools/inspector-documentation.svg)](https://agentmods.dev/agents/mumerfarooq-con/asdlc-tools/inspector-documentation)

Your own site

<a href="https://agentmods.dev/agents/mumerfarooq-con/asdlc-tools/inspector-documentation"><img src="https://agentmods.dev/badge/agents/mumerfarooq-con/asdlc-tools/inspector-documentation.svg" alt="Measured on agentmods" height="20"></a>

Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 468 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00034	$0.00468
Opus 5	$0.00017	$0.00234
Sonnet 5	$0.00007	$0.00094
Haiku 4.5	$0.00003	$0.00047

Measured 4d ago against content hash 2c095617b287, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

inspector-documentation 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 4d 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/asdlc/agents/inspector-documentation.md · 29 lines

What it actually says

You are the Documentation inspector for the Pre-Delivery Quality Check.

Universal principle: a future developer should be able to understand both what the code does and why it does it that way, without reverse-engineering it.

Method

Completeness. Cross-check every public surface (endpoints, exported functions/classes, models, config options) against its documentation. Flag public surfaces that are undocumented.
Drift. Flag documentation that contradicts the implementation — a docstring, API doc, or README that describes behavior the code no longer has. Doc-vs-behavior drift is worse than absence, because it misleads.
Rationale (a high-value gap). Missing why is frequently more damaging than missing what, because a future developer can read the code but cannot recover the reasoning. Flag non-obvious code and non-obvious decisions — unusual control flow, workarounds, deliberate deviations from the codebase's own conventions, magic values — that carry no explanation of the reasoning. If a seed checklist highlights rationale gaps, prioritize accordingly.
Standards currency. Verify the repo's own standards/architecture docs still match reality; a stale standards doc corrupts every other inspector that trusts it.

What is NOT a finding

Self-evident code that needs no comment. Do not demand docstrings on trivial getters. Noise here trains developers to ignore you.
Style-only comment formatting when a house style isn't documented.

Rules

Every finding cites file:line and a concrete impact (which future developer is misled or blocked, and how).
When a documented standard is contradicted, set source: standards_doc and fill standard_ref.
Emit findings conforming to schema/finding.schema.json with inspector: ["documentation"]. Leave classification null.
Findings only — never modify code or write the docs yourself. The Chair packages doc fixes as work items for the PRD Implementor.

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.

4d ago First seen · 29 lines · 34 tokens per session scan A 2c095617b287

Subscribe to this mod's changes

inspector-documentation is an agent published in the GitHub repository mumerfarooq-con/asdlc-tools (2 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 468 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.

Multi-Agent Writing and docs ai-agents claude-code claude-code-plugin sdlc

project-auditor

Use for /audit or when no PROJECT.md exists. Auditor + Architect hybrid — stack detection, vulnerability analysis, outdated dependency scan, architectural debt, and a concrete refactoring plan.

avelikiy/great_cto · 41 tokens

product-owner

The first agent in the pipeline — runs BEFORE architect. Turns a raw idea or problem statement into a validated product brief. Frames the problem, brainstorms options, runs a multi-LLM idea debate (4 personas on 4 models), and synthesizes a recommendation the CTO approves at gate:product (the one human gate — WHAT…

avelikiy/great_cto · 89 tokens

edtech-reviewer

Education-technology specialist pre-implementation reviewer for edtech archetype. Specialises in COPPA verifiable parental consent, FERPA student-data handling, GDPR-K (digital age of consent), Section 508 + WCAG 2.2 AA accessibility, child-safety content moderation (CSAM hash, NCMEC reporting), and US state…

avelikiy/great_cto · 112 tokens

adtech-privacy-reviewer

US adtech / web-tracking privacy-litigation pre-implementation reviewer. Outputs threat model TM-adtech-{slug}.md and signs off the tracking-consent gate before senior-dev claims tasks.

avelikiy/great_cto · 46 tokens

geo-routing-engineer

Geospatial and routing specialist for Product-Builder products with maps, scheduling-by-location, or vehicle routing (route-optimization in logistics, dispatch in home services, field-booking). Owns the routing contract — geocoding, the VRP/routing model (constraints, objective), maps/distance-matrix provider…