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/geo-mena/distill/distill-designgit clone --depth 1 https://github.com/geo-mena/distillWrote 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/geo-mena/distill/distill-design)<a href="https://agentmods.dev/rules/geo-mena/distill/distill-design"><img src="https://agentmods.dev/badge/rules/geo-mena/distill/distill-design.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 | $0.00000 | $0.00301 |
| Opus 5 | $0.00000 | $0.00151 |
| Sonnet 5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
distill-design 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 5d 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
Use the canonical distill-design skill from plugins/distill-design/. Cursor support is rules-based guidance, not native Agent Skills support.
When the user asks for a long-form ML/AI explainer, a hand-drawn diagram, a cloud-architecture SVG, a slide deck, or product styling in Distill voice, read plugins/distill-design/SKILL.md and follow its decision tree. For deep design rules (color values, typography, voice samples, iconography), read plugins/distill-design/DESIGN-SYSTEM.md.
Hard constraints: no emoji, no marketing superlatives, no exclamation points in body, no gradients, body color rgba(0,0,0,0.8), pure #000 reserved for h1, strokes 1.5–2px in #666 with rounded caps. Pull design tokens from plugins/distill-design/tokens/colors_and_type.css; reuse TSX primitives from plugins/distill-design/ui_kits/article/; copy service icons from plugins/distill-design/resources/diagrams/_service-icons.svg inline into consumer SVGs.
The article kit needs HTTP serving (python3 -m http.server from the plugin root) — file:// blocks Babel standalone XHR.
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.
- 5d ago First seen · 14 lines · 301 tokens per session scan A 6b2c5dca7f7e
distill-design is a cursor rule published in the GitHub repository geo-mena/distill (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 301 tokens. 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
slopmop-barnacle
Report slop-mop tool friction — when sm itself blocks valid work, file a barnacle instead of routing around it.
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.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.