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 rules/axcient/public-gateway-mcp/code-review-agentsgit clone --depth 1 https://github.com/Axcient/public-gateway-mcpWrote 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/axcient/public-gateway-mcp/code-review-agents)<a href="https://agentmods.dev/rules/axcient/public-gateway-mcp/code-review-agents"><img src="https://agentmods.dev/badge/rules/axcient/public-gateway-mcp/code-review-agents.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 | $0.00232 | $0.00232 |
| Opus 5 | $0.00116 | $0.00116 |
| Sonnet 5 | $0.00046 | $0.00046 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
code-review-agents 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 3d 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
Code reviews enforce AGENTS.md
Whenever you run or delegate a code review (including the code-reviewer
subagent / Task tool, /code-reviewer, or the stop-hook review loop):
- Read the full current
AGENTS.mdfrom disk before judging the diff. Do not rely on memory or a partial summary. - Enforce every applicable AGENTS.md rule on the change-set (MCP server
globals, OpenAPI docs passed unchanged, one httpx client per mount, no
BaseException, no mocking, full-object asserts, naming,justtooling, etc.). - Treat AGENTS.md violations as High / blocking unless clearly stylistic.
- Tell the reviewer (in the Task prompt) to read
AGENTS.mdfirst and to confirmAGENTS.md reviewed: yesin its report. just check-alldoes not replace this — tooling does not enforce AGENTS.md conventions.
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.
- 3d ago First seen · 22 lines · 232 tokens per session scan A 5d807e1478dc
code-review-agents is a cursor rule published in the GitHub repository Axcient/public-gateway-mcp (0 stars, last pushed 9d ago), licensed Apache-2.0. It adds 232 tokens to every session, about $0.0012 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-09-01.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.