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/michele-prandina/ClaudE2EWrote 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/michele-prandina/claude2e/designer)<a href="https://agentmods.dev/rules/michele-prandina/claude2e/designer"><img src="https://agentmods.dev/badge/rules/michele-prandina/claude2e/designer/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/michele-prandina/claude2e/designer"><img src="https://agentmods.dev/badge/rules/michele-prandina/claude2e/designer.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.00037 | $0.02478 |
| Opus 5.5 | $0.00015 | $0.00991 |
| Sonnet 5.5 | $0.00007 | $0.00496 |
| Haiku 4.5 | $0.00004 | $0.00248 |
Grade A, and why
designer 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 2mo 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2mo ago First seen · 290 lines · 37 tokens per session scan A 67acc52e74a6
designer is a cursor rule published in the GitHub repository michele-prandina/ClaudE2E (8 stars, last pushed 8mo ago), with no licence file. It adds 37 tokens to every session and 2,478 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
react-chakra-ui-cursorrules-prompt-file
Cursor rules for React development with Chakra UI integration.
best_practices
Advanced Best Practices covering Error Handling, Environment Variables, Performance, and Accessibility rules.
humanizer
Humanize AI-sounding prose, rewrite in a writer's voice, and conservatively clean suspicious invisible Unicode in supplied prose. Use whenever the user wants to humanize, de-slop, de-AI, or de-robotify text; fix writing that sounds like an LLM, corporate, salesy, generic, or off; make a draft sound like them or a…
06-buttons-cta
Buttons, CTAs, button hierarchy, sizes, states, filled/outlined/text variants. Use when creating buttons, call-to-action elements, or interactive action components.
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.