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/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/self-review)<a href="https://agentmods.dev/rules/axcient/public-gateway-mcp/self-review"><img src="https://agentmods.dev/badge/rules/axcient/public-gateway-mcp/self-review.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.1 | $0.00388 | $0.00388 |
| Opus 5 | $0.00194 | $0.00194 |
| Sonnet 5 | $0.00078 | $0.00078 |
| Haiku 4.5 | $0.00039 | $0.00039 |
Grade A, and why
self-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 6d 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
Mandatory self-review before completing work
Before declaring any code change complete, you MUST:
- Read
AGENTS.mdand review every rule against your changes - Specifically verify (including current MCP / testing rules in AGENTS.md):
mcpis a module-level global — assigned at import time outside any function; FastMCP CLI-importable- OpenAPI docs unchanged — pass loaded specs into
from_openapias-is; no copy/deep-copy/path rewrite - One
httpx.AsyncClientper OpenAPI mount —base_urlfrom that spec’sservers[0].url; close all in lifespan/finally - No
BaseException— usetry/finallyfor cleanup - No mocking — no monkeypatch/MockTransport/fake clients; prefer DI + real local HTTP
- Assert full objects — never assert partial responses (single fields, lengths, filtered projections)
- No enumerated variables — use lists, not
x1,x2 - No
time.sleep— never add sleep calls anywhere - No raw DB access in tests — all database operations go through
PostgresInteractorwhen DB exists
- Only after confirming compliance with ALL rules, report the work as done
If any rule is violated, fix it before reporting completion. Do not rely on just check-all alone — it checks tooling (lint, types, coverage) but NOT AGENTS.md conventions.
When a code review runs, the reviewer must also read AGENTS.md first and enforce it (see .cursor/rules/code-review-agents.mdc).
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.
- 6d ago First seen · 26 lines · 388 tokens per session scan A 228bfce6e59d
self-review is a cursor rule published in the GitHub repository Axcient/public-gateway-mcp (0 stars, last pushed 13d ago), licensed Apache-2.0. It adds 388 tokens to every session, about $0.0019 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
clean-code-reviewer
Eliminates technical debt using SOLID, DRY, YAGNI, and Addy Osmani production-grade engineering principles. / TR: SOLID, DRY, YAGNI ve Addy Osmani üretim seviyesi mühendislik ilkeleri ile kod kalitesini denetleyen yetenek.
sweep-benchmarks
Audit xrspatial modules for asv benchmark coverage gaps: missing benchmarks, backend parameterization gaps, unrepresentative inputs, broken or silently-skipped benchmarks.
code-review
BMAD BMM Agent: code-review.
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.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.