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/Caldis/react-zmageWrote 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/caldis/react-zmage/react-zmage)<a href="https://agentmods.dev/rules/caldis/react-zmage/react-zmage"><img src="https://agentmods.dev/badge/rules/caldis/react-zmage/react-zmage/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/caldis/react-zmage/react-zmage"><img src="https://agentmods.dev/badge/rules/caldis/react-zmage/react-zmage.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.00095 | $0.00095 |
| Opus 5.5 | $0.00038 | $0.00038 |
| Sonnet 5.5 | $0.00019 | $0.00019 |
| Haiku 4.5 | $0.00010 | $0.00010 |
Grade A, and why
react-zmage 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
Read AGENTS.md before editing. Keep changes scoped to the requested behavior, preserve the public API contract, and verify with the relevant pnpm scripts.
Treat react-zmage as a client-side React component package. Do not invent hosted API, OAuth, API key, webhook, MCP, account, or server-side image-processing behavior.
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 · 11 lines · 95 tokens per session scan A e9ea7e039a97
react-zmage is a cursor rule published in the GitHub repository Caldis/react-zmage (945 stars, last pushed 5mo ago), licensed MIT. It adds 95 tokens to every session, about $0.0004 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-30.
Other cursor rules, from other repositories
verify
Verify Plate packages, browser editor behavior, CLI artifacts, collaboration and tests at their actual owners. Load before selecting, changing or waiving proof, writing tests or claiming a fix works.
sync-shadcn
Sync upstream shadcn docs or registry protocol into Plate with exact source ranges, preserved forks, accepted apply rows and complete baseline accounting.
plate-plugins
Build or change Plate plugins and packages with semantic ownership, inferred contracts, React adapters and package proof. Use for plugin fields, options, serializers and cross-package features.
testing-react
Testing React components — React Testing Library, hooks, context, async, accessibility. Extends core/rules/testing.mdc with React-specific patterns.
component-audit-rubric
React/TS component audits — five-axis rubric, evidence, artifacts.
hooks-and-effects
React anti-patterns R1, R2, R3, R8, R13, R15 — useEffect cleanup, stale closures, dependency arrays, conditional hooks, ref listener cleanup. Load on a review hit for any of these codes, or when writing hooks and effects.