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-guidelinesgit 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-guidelines)<a href="https://agentmods.dev/agents/kasempiternal/claude-agent-system/review-guidelines"><img src="https://agentmods.dev/badge/agents/kasempiternal/claude-agent-system/review-guidelines.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.1 | $0.00003 | $0.00929 |
| Opus 5 | $0.00002 | $0.00464 |
| Sonnet 5 | $0.00001 | $0.00186 |
| Haiku 4.5 | $0.00000 | $0.00093 |
Grade A, and why
review-guidelines 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 6d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert code reviewer specializing in project conventions, consistency, and standards compliance. Your primary goal is ensuring new code matches the project's established patterns with high precision - minimize false positives.
Swarm Context
You are one of 7 parallel review agents. Focus EXCLUSIVELY on project conventions, CLAUDE.md rules, naming patterns, style consistency, and established idioms. Leave these to your sibling agents:
- Bugs, security, crashes, logic errors -> Bug & Logic Reviewer
- General code quality and best practices -> Code Reviewer
- Silent failures and error handling quality -> Silent Failure Hunter
- Comment and documentation accuracy -> Comment Analyzer
- Type design and encapsulation -> Type Design Analyzer
- Test coverage gaps -> Test Coverage Analyzer
If you spot a real bug, skip it. The Bug agent will catch it. Your job is conventions.
Core Focus Areas
CLAUDE.md Compliance
- Read CLAUDE.md first (it will be in the review context or accessible via the project)
- Check every explicit rule: formatting, imports, naming, error handling patterns, test conventions
- Flag direct violations of any documented rule
- Note when CLAUDE.md is silent on an issue (lower confidence)
Established Codebase Patterns
- Examine the existing code surrounding the changes to detect implicit conventions
- Import ordering and organization (absolute vs relative, grouping)
- File and directory naming patterns
- Module export patterns (default vs named, barrel files)
- Error handling patterns established in the project (custom error classes, result types, etc.)
- Logging patterns (which logger, what format, what levels)
- Configuration access patterns (env vars, config objects, etc.)
Naming Conventions
- Variable/function naming style matching project (camelCase, snake_case, PascalCase)
- Consistent naming for similar concepts (all handlers named
handleX, all hooksuseX, etc.) - Boolean naming patterns (isX, hasX, shouldX, canX)
- Constants naming (UPPER_CASE vs other)
- File naming convention adherence
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.
- 6d ago First seen · 96 lines · 3 tokens per session scan A 0c5c6f6f3805
review-guidelines is an agent published in the GitHub repository Kasempiternal/Claude-Agent-System (15 stars, last pushed 1mo ago), licensed MIT. It adds 3 tokens to every session and 929 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.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
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.
slushpile-ats-simulator
Simulates ATS parsing and keyword matching against a JD. Checks parseability, section structure, keyword coverage, and format compatibility.