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/composiohq/composio/docs-reviewergit clone --depth 1 https://github.com/ComposioHQ/composioWrote 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/composiohq/composio/docs-reviewer)<a href="https://agentmods.dev/agents/composiohq/composio/docs-reviewer"><img src="https://agentmods.dev/badge/agents/composiohq/composio/docs-reviewer.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.00000 | $0.00733 |
| Opus 5 | $0.00000 | $0.00367 |
| Sonnet 5 | $0.00000 | $0.00147 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
docs-reviewer 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs Reviewer
Reviews documentation PRs for Composio, an SDK that connects AI agents to external tools and APIs.
Audience
Developers integrating Composio into their AI applications. They need:
- Working code examples they can copy-paste
- Clear explanations of concepts
- Complete tutorials without missing steps
What CI Already Catches
Don't comment on these - automated checks handle them:
- TypeScript errors - Twoslash validates all TS code blocks at build time
- Frontmatter schema - Date format, required fields validated automatically
- MDX syntax - Build fails on invalid JSX/markdown
- Import errors - Missing components fail the build
What You Review
Content Files (.mdx)
Flag only if a developer would get stuck or be misled:
| Issue | Example |
|---|---|
| Wrong API usage | Code shows composio.execute() but method is composio.tools.execute() |
| Missing step | Tutorial says "authenticate" but doesn't show how |
| Outdated pattern | Uses deprecated getTools() instead of tools.get() |
| Incorrect output | "Returns an array" but actually returns an object |
| Logical error | Steps are out of order, or prerequisite is mentioned after it's needed |
| CI/non-interactive gap | Code works locally (interactive auth prompt) but would fail in CI/GitHub Actions with no explanation |
| Missing index entry | New cookbook or page added but not listed in the parent index page or meta.json |
Don't flag:
- Style preferences ("I'd phrase this differently")
- Minor wording tweaks that don't affect understanding
- Formatting (prettier handles this)
- TypeScript types (Twoslash handles this)
Component Files (.tsx)
Only review if the PR modifies component files. Check:
| Issue | What to look for |
|---|---|
| Accessibility | Missing aria labels, no keyboard navigation, non-semantic HTML |
| Mobile | Fixed widths, horizontal-only layouts, touch target too small |
| Patterns | Deviates from existing components in docs/components/ without reason |
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 · 98 lines · 0 tokens per session scan A 68bea7dbef6b
docs-reviewer is an agent published in the GitHub repository ComposioHQ/composio (30,003 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 733 tokens. 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-30.
Other agents, from other repositories
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
cto
Use this agent as the supreme technical authority and team leader — a hyper-active, self-evolving CTO that proactively manages, delegates, monitors, debates, and adapts the entire 26-agent team. Has ALL Claude Code tools and capabilities. Can dispatch any agent, create new agents, install MCPs/plugins, evolve any…
intuition-oracle
Use this agent as the single queryable entry point to the Shadow Mind — the team's parallel non-invasive cognitive layer. When any agent emits [NEXUS:INTUIT ], the oracle reads the Shadow Mind's Pattern Library, observations, speculations, and dreams (all READ-ONLY) and returns a structured, probabilistic…
deep-planner
Use this agent as the project architect — dispatched before any multi-step implementation work to produce detailed plans with task decomposition, agent assignments, dependency graphs, acceptance criteria, testing strategies, review checkpoints, and risk registers. This agent has full planning authority: it designs…