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/saralobo/rules-design-bibleWrote 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/saralobo/rules-design-bible/17-icons)<a href="https://agentmods.dev/rules/saralobo/rules-design-bible/17-icons"><img src="https://agentmods.dev/badge/rules/saralobo/rules-design-bible/17-icons/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/saralobo/rules-design-bible/17-icons"><img src="https://agentmods.dev/badge/rules/saralobo/rules-design-bible/17-icons.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.07452 |
| Opus 5 | $0.00018 | $0.03726 |
| Sonnet 5 | $0.00007 | $0.01490 |
| Haiku 4.5 | $0.00004 | $0.00745 |
Grade A, and why
17-icons 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 9d 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.
- 9d ago First seen · 740 lines · 37 tokens per session scan A e427bf94109a
17-icons is a cursor rule published in the GitHub repository saralobo/rules-design-bible (24 stars, last pushed 5mo ago), with no licence file. It adds 37 tokens to every session and 7,452 once invoked, about $0.0002 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
compress-md-landing-page-prompt.crux
⟦CRUX:compress-md-landing-page-prompt.md Ρ{compress.md landing page} target=single static page for CRUX-Compress repo=github.com/zotoio/CRUX-Compress domain=compress.md; status=EXPERIMENTAL! msg="Reclaim ≤80% ctx window. CRUX→semantic core extraction" journey{land→compression viz»scroll»explore»expand spec»install}.
components
Rules for component usage - which component libraries are allowed (shadcn/ui, Aceternity, Kibo, Magic UI, etc.), reuse over recreation, table implementation standards, and component modularization for both new features and existing components.
006-ui-styling
Enforce consistent UI styling practices across the codebase for a cohesive visual experience, maintainability, and performance.
011-accessibility-inclusion
Implement accessibility features when building interfaces to ensure usability for all users including those with disabilities.
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.