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 commands/vishnu2kmohan/mcp-server-langgraph/docs-auditgit clone --depth 1 https://github.com/vishnu2kmohan/mcp-server-langgraphWrote 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/commands/vishnu2kmohan/mcp-server-langgraph/docs-audit)<a href="https://agentmods.dev/commands/vishnu2kmohan/mcp-server-langgraph/docs-audit"><img src="https://agentmods.dev/badge/commands/vishnu2kmohan/mcp-server-langgraph/docs-audit.svg" alt="Measured on agentmods" 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 | $0.00018 | $0.02357 |
| Opus 5 | $0.00009 | $0.01179 |
| Sonnet 5 | $0.00004 | $0.00471 |
| Haiku 4.5 | $0.00002 | $0.00236 |
Grade A, and why
docs-audit 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 3d 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 — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Comprehensive Documentation Audit
Conduct a thorough analysis of all documentation in this codebase to ensure everything is up to date, well-organized, and tidy.
Scope
Analyze the following documentation areas:
1. Mintlify Documentation (Primary)
- Configuration: Validate
docs/docs.jsonstructure and completeness - Navigation: Verify all navigation entries reference existing files
- MDX Files: Check all
.mdxfiles indocs/directory - Cross-references: Validate internal links between documentation pages
- Code snippets: Ensure code examples are current and functional
- Missing pages: Identify navigation items without corresponding files
- Orphaned files: Find documentation files not referenced in navigation
2. Root-Level Documentation
README.md- Main project documentationTESTING.md- Testing guidelinesSECURITY.md- Security policiesCODE_OF_CONDUCT.md- Community guidelinesDEVELOPER_ONBOARDING.md- Developer setupREPOSITORY_STRUCTURE.md- Project organizationMIGRATION.md- Migration guidesROADMAP.md- Project roadmapCHANGELOG.md- Change history- Other root
.mdfiles
Validate:
- Accuracy of information
- Broken external links
- Outdated version references
- Consistency with current codebase state
3. Architecture Decision Records (ADRs)
- Compare
adr/*.mdwithdocs/architecture/*.mdx - Verify sync between source ADRs and Mintlify versions
- Check for missing or outdated ADRs
- Validate ADR numbering and naming consistency
4. Internal Documentation
docs-internal/*.md- Internal technical documentation- Verify alignment with current implementation
- Check for outdated information
5. Specialized Documentation
examples/README.md- Example documentationdeployments/README.md- Deployment guidesmonitoring/README.md- Monitoring setupconfig/README.md- Configuration documentationtests/README.md- Testing documentationrunbooks/README.md- Operational runbooks
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.
- 3d ago First seen · 327 lines · 18 tokens per session scan A 5e878332dc85
docs-audit is a command published in the GitHub repository vishnu2kmohan/mcp-server-langgraph (4 stars, last pushed 10d ago), licensed MIT. It adds 18 tokens to every session and 2,357 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 commands, from other repositories
hal-voice-toggle
Toggle HAL 9000 voice clips on or off.
deps-age
Analyze dependency freshness and maintenance activity.
audit-code
When /audit-code [target] is invoked, immediately execute the following steps to analyze code quality, security, and adherence to project standards.
designer
UI/UX design with Memory coordination for consistent experiences.
pipeline-generate
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with pipeline generate in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.
terraform-scaffold
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with terraform scaffold in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.