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.
git clone --depth 1 https://github.com/lxb12123/agent-plugin-kitWrote 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/rules/lxb12123/agent-plugin-kit/review)<a href="https://agentmods.dev/rules/lxb12123/agent-plugin-kit/review"><img src="https://agentmods.dev/badge/rules/lxb12123/agent-plugin-kit/review/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/lxb12123/agent-plugin-kit/review"><img src="https://agentmods.dev/badge/rules/lxb12123/agent-plugin-kit/review.svg" alt="Reviewed on agentmods" width="80" 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.00033 | $0.00260 |
| Opus 5.5 | $0.00013 | $0.00104 |
| Sonnet 5.5 | $0.00007 | $0.00052 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
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 1mo 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.
What it actually says
/review — Code review
You are a strict but pragmatic code reviewer.
Steps
- Run the deterministic script to get the changes (0-token reasoning):
node skills/review/scripts/collect-diff.mjs HEADIt outputs JSON:{ files: string[], diff: string }. - If
filesis empty, reply "no changes to review" and stop. - Only when needed, load
skills/review/reference/review-standards.mdas the review standard (gene ③: load on demand). - For the
diff, give item by item: the problem location (file:line), severity (blocker/warning/nit), the reason, and a fix suggestion. - End with a one-line overall verdict (ready to merge / needs changes).
Constraints
- Review only the changes within the diff; do not vaguely rewrite the whole file.
- For deterministic facts (which files changed), use the script results — do not guess.
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.
- 1mo ago First seen · 23 lines · 33 tokens per session scan A d14f95b5746d
review is a cursor rule published in the GitHub repository lxb12123/agent-plugin-kit (1 stars, last pushed 3mo ago), licensed MIT. It adds 33 tokens to every session and 260 once invoked, about $0.0001 per session on Opus 5.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-31.
Other cursor rules, from other repositories
risk-factors
Risk scoring factor definitions and weights for PR review dispatch.
context-delegate
Context Gatherer & External LLM Prompt Generator.
jg-pr-review
PR review categories and decision rules.
refactorer
Refactorer agent.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.