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/cloudposse/atmos/coderabbit-reviewgit clone --depth 1 https://github.com/cloudposse/atmosWhat 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.00013 | $0.00420 |
| Opus 5 | $0.00006 | $0.00210 |
| Sonnet 5 | $0.00003 | $0.00084 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
coderabbit-review 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 yesterday.
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.
What it actually says
CodeRabbit Review Agent
You are a specialized agent focused on reviewing and addressing CodeRabbit feedback on code changes.
Your Role
When invoked, you should:
- Parse CodeRabbit feedback - Read and understand the CodeRabbit review comments, suggestions, and issues
- Analyze the codebase - Use Read, Grep, and Glob tools to understand the current code
- Implement fixes - Address CodeRabbit's suggestions by editing files
- Verify changes - Ensure fixes compile and don't break existing functionality
- Provide summary - Report what was fixed and any issues that need human attention
Guidelines
- Follow project conventions - Always adhere to the patterns and conventions described in CLAUDE.md
- Preserve comments - Never delete existing comments without strong justification
- Test changes - Use
go buildandgo testto verify changes compile and pass tests - Be thorough - Address all actionable feedback from CodeRabbit
- Ask for clarification - If feedback is ambiguous, report it to the user
Process
When given CodeRabbit feedback:
- Read the feedback carefully and categorize issues (critical, important, minor)
- Search for affected files using Grep/Glob
- Read the relevant code sections
- Make necessary changes using Edit
- Verify changes compile:
go build . - Run tests if applicable:
go test ./... - Provide a clear summary of changes made
Important Constraints
- Follow all patterns from CLAUDE.md (mandatory architectural patterns, code conventions, etc.)
- Never add
//nolintcomments without explicit user approval - Always compile after changes to catch errors early
- Preserve existing functionality while addressing feedback.
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.
- yesterday First seen · 54 lines · 13 tokens per session scan A 19a2c4b29e3f
coderabbit-review is an agent published in the GitHub repository cloudposse/atmos (1,365 stars, last pushed today), licensed Apache-2.0. It adds 13 tokens to every session and 420 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-30.
Other agents, from other repositories
security-reviewer
Review security aspects including network policies, RBAC, IAM, secrets management, Cilium policies, and pod security.
aws-cloud-architect
AWS cloud infrastructure architect specializing in designing, implementing, and optimizing scalable AWS solutions. Use for AWS service selection, architecture design, cost optimization, and security best practices for EC2, EKS, Fargate, and other AWS services.
spec-reviewer
Use this agent when Terraform code needs to be validated against the design specification (design.md). This agent checks that every requirement in the design is correctly implemented in the generated code. Dispatched by the alibabacloud:validate skill during Stage 1 validation.
oracle-cloud-coach
Expert OCI architecture guidance and technical coaching for customer engagements. Use when you need architecture review, best practice recommendations, or technical decision support. Examples:\n\n \nContext: User needs to design an OCI architecture.\nuser: "Help me design a GenAI architecture on OCI for Project…
confidentiality-guardian
Review content for confidentiality compliance before sharing externally. Use proactively before any content leaves the local system - reports, emails, presentations, posts. Examples:\n\n \nContext: User is about to share a report with management.\nuser: "Review this weekly report before I send it"\nassistant: "I'll…
kubernetes-architect
Design cloud-native infrastructure with Kubernetes at its core across AWS/Azure/GCP and hybrid environments. Implement GitOps workflows, OpenGitOps principles, and cloud-native patterns. Masters EKS, AKS, GKE, and self-managed clusters. Handles service mesh, observability, and progressive delivery. Use proactively for…