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/cursor-plugin/coderabbit-reviewgit clone --depth 1 https://github.com/coderabbitai/cursor-pluginWhat 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.00014 | $0.00762 |
| Opus 5 | $0.00007 | $0.00381 |
| Sonnet 5 | $0.00003 | $0.00152 |
| Haiku 4.5 | $0.00001 | $0.00076 |
Grade C, and why
coderabbit-review scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://cli.coderabbit.ai/install.sh | sh Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://cli.coderabbit.ai/install.sh | sh How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CodeRabbit Review
Run a CodeRabbit review using the arguments the user supplied.
Context Checks
Run:
git rev-parse --is-inside-work-tree
coderabbit --version
coderabbit auth status --agent
If Git is unavailable or the current directory is not a Git repository, tell the user that CodeRabbit review needs a Git repository.
If CodeRabbit CLI is not installed, install it from CodeRabbit's official installer:
curl -fsSL https://cli.coderabbit.ai/install.sh | sh
export PATH="$HOME/.local/bin:$PATH"
coderabbit --version
If coderabbit --version still fails after refreshing PATH, try $HOME/.local/bin/coderabbit --version. Use the resolved binary path for subsequent CodeRabbit commands in this session. If that still fails, report the exact failure and stop.
If CodeRabbit is not authenticated, start the agent auth flow:
coderabbit auth login --agent
coderabbit auth status --agent
Only continue after coderabbit auth status --agent succeeds.
Build Review Command
Default review:
coderabbit review --agent
Map user arguments:
allmeans-t all.committedmeans-t committed.uncommittedmeans-t uncommitted.--base <branch>passes the base branch.--base-commit <sha>passes the base commit.--dir <path>passes a review directory after verifying it is a Git repository.- Existing instruction files such as
AGENTS.md,cursor.md, or.coderabbit.yamlcan be passed with-c <file>after confirmingcoderabbit review --helpsupports-c.
Before using --dir, run:
git -C <path> rev-parse --is-inside-work-tree
Before using -c, confirm each file exists and is relevant to the review.
Present Results
Parse CodeRabbit agent output. Ignore status events in the user-facing summary. If the CLI returns an error, report it directly and do not substitute a manual review. If the error is an install or authentication failure, guide the user through fixing the setup step by step, then resume the review once setup succeeds. If the error is a rate limit, share the exact message, stop, and offer to re-run the review once the limit resets.
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 · 88 lines · 14 tokens per session scan C f9c923a38b3a
coderabbit-review is a command published in the GitHub repository coderabbitai/cursor-plugin (2 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 762 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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.