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/coderabbitai/skills/coderabbit-reviewgit clone --depth 1 https://github.com/coderabbitai/skillsWhat 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.00009 | $0.00603 |
| Opus 5 | $0.00005 | $0.00302 |
| Sonnet 5 | $0.00002 | $0.00121 |
| Haiku 4.5 | $0.00001 | $0.00060 |
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 2d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CodeRabbit Code Review
Run an AI-powered code review using CodeRabbit.
Context
- Current directory: !
pwd - Git repo: !
git rev-parse --is-inside-work-tree 2>/dev/null && echo "Yes" || echo "No" - Branch: !
git branch --show-current 2>/dev/null || echo "detached HEAD" - Has changes: !
git status --porcelain 2>/dev/null | head -1 | grep -q . && echo "Yes" || echo "No"
Instructions
Review code based on: $ARGUMENTS
Prerequisites Check
Skip these checks if you already verified them earlier in this session.
Otherwise, run:
coderabbit --version 2>/dev/null && coderabbit auth status 2>&1 | head -3
If CLI not found, tell user:
CodeRabbit CLI is not installed. Install it from the official docs:
Prefer a package manager or a verified binary, then restart your shell and try again.
If "Not logged in", tell user:
You need to authenticate. Run in your terminal:
coderabbit auth loginThen try again.
Run Review
Once prerequisites are met:
# type defaults to "all"; add --base and --dir only when specified
args=(review --agent -t "${type:-all}")
[ -n "${base:-}" ] && args+=(--base "$base")
[ -n "${dir:-}" ] && args+=(--dir "$dir")
coderabbit "${args[@]}"
Where type, base, and dir come from $ARGUMENTS:
all(default) - All changescommitted- Committed changes onlyuncommitted- Uncommitted only
Add --base <branch> only when a base branch is specified.
Add --dir <path> only when a review directory is specified. The directory must contain an initialized Git repository; verify it first:
git -C "$dir" rev-parse --is-inside-work-tree
Present Results
Group findings by severity:
- Critical - Security vulnerabilities, data loss risks, crashes
- Warning - Bugs, performance issues, anti-patterns
- Info - Style issues, suggestions, minor improvements
Offer to apply fixes from the --agent findings when the output includes actionable remediation details.
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.
- 2d ago First seen · 82 lines · 9 tokens per session scan A d2f0c42d8724
coderabbit-review is a command published in the GitHub repository coderabbitai/skills (162 stars, last pushed 15d ago), licensed MIT. It adds 9 tokens to every session and 603 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.