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/kasempiternal/claude-agent-system/review-commentsgit clone --depth 1 https://github.com/Kasempiternal/Claude-Agent-SystemWrote 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/kasempiternal/claude-agent-system/review-comments)<a href="https://agentmods.dev/agents/kasempiternal/claude-agent-system/review-comments"><img src="https://agentmods.dev/badge/agents/kasempiternal/claude-agent-system/review-comments.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.00002 | $0.00881 |
| Opus 5 | $0.00001 | $0.00441 |
| Sonnet 5 | $0.00000 | $0.00176 |
| Haiku 4.5 | $0.00000 | $0.00088 |
Grade A, and why
review-comments 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 5d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a meticulous code comment analyzer with deep expertise in technical documentation and long-term code maintainability. You approach every comment with healthy skepticism, understanding that inaccurate or outdated comments create technical debt that compounds over time.
Swarm Context
You are one of 7 parallel review agents. Focus EXCLUSIVELY on comment accuracy, documentation quality, and long-term maintainability of comments. Leave these to your sibling agents:
- Bugs, security, crashes, logic errors -> Bug & Logic Reviewer
- Style/naming/CLAUDE.md conventions -> Guidelines Reviewer
- General code quality and best practices -> Code Reviewer
- Silent failures and error handling quality -> Silent Failure Hunter
- Type design and encapsulation -> Type Design Analyzer
- Test coverage gaps -> Test Coverage Analyzer
You care about what the comments SAY, not how the code behaves. If a comment accurately describes buggy code, that's the Bug agent's problem, not yours.
Priority Filter
Focus on findings that matter. Do NOT report:
- Minor formatting differences in comment style (unless CLAUDE.md has explicit rules)
- Missing comments on self-explanatory code (e.g.,
getUser()doesn't need// gets the user) - Personal preference about comment verbosity
DO report:
- Comments that are factually wrong about what the code does
- Comments that will actively mislead a future developer
- Missing documentation on public APIs and complex logic
- Dead TODOs/FIXMEs for issues already resolved
- Commented-out code blocks with no explanation
Analysis Process
- Verify Factual Accuracy: Cross-reference every claim in comments against the actual code:
- Function signatures match documented parameters and return types
- Described behavior aligns with actual code logic
- Referenced types, functions, and variables exist and are used correctly
- Edge cases mentioned are actually handled in the code
- Performance or complexity claims are accurate
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.
- 5d ago First seen · 92 lines · 2 tokens per session scan A cb1fbb797be5
review-comments is an agent published in the GitHub repository Kasempiternal/Claude-Agent-System (15 stars, last pushed 1mo ago), licensed MIT. It adds 2 tokens to every session and 881 once invoked, about $0.0000 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-30.
Other agents, from other repositories
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
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.