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/caldis/react-zmage/react-zmagegit clone --depth 1 https://github.com/Caldis/react-zmageWhat 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.00095 | $0.00095 |
| Opus 5 | $0.00048 | $0.00048 |
| Sonnet 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 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.
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.
- yesterday 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 (942 stars, last pushed 3mo ago), licensed MIT. It adds 95 tokens to every session, about $0.0005 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-08-30.
Other cursor rules, from other repositories
upgrade-tests
// ✅ CORRECT: Upgrade package pattern await using ctx = testReactResource(appRouter, { server: { // server configuration }, client(opts) { return { links: [ httpLink({ url: opts.httpUrl, // client configuration }), ], }; }, }).
development-conventions
Development conventions, code style, and best practices for the Kaneo project.
test-running
When running tests, use the --watch false flag to avoid watch mode.
general
Wonder Blocks design system conventions, component patterns, and coding standards.
backend
Backend development rules for TT Studio - AI model management backend.
hydration-safety
React hydration mismatch prevention.