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/stass/blewWrote 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/stass/blew/design)<a href="https://agentmods.dev/rules/stass/blew/design"><img src="https://agentmods.dev/badge/rules/stass/blew/design/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/stass/blew/design"><img src="https://agentmods.dev/badge/rules/stass/blew/design.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.00186 | $0.00186 |
| Opus 5.5 | $0.00074 | $0.00074 |
| Sonnet 5.5 | $0.00037 | $0.00037 |
| Haiku 4.5 | $0.00019 | $0.00019 |
Grade A, and why
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 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.
What it actually says
When this rule loads, input: "Rule loaded: design.mdc." The project architecture and design is described in DESIGN.md Please analyze @DESIGN.md before implementing changes and make your plans based on that.
When making architectural changes, make sure to update DESIGN.md as well so it reflects the changes made.
Don't hedge or add fallback values -- make a reasoned decision on what values should be available and use them, throw errors when unexpected things happend instead of adding fallbacks
Don't use emojis in documentation or logs.
Whenever we update user facing functionality or behvaior update README.md to reflect the changes.
For every new change make sure tests still pass. If we are fixing a bug -- add a new test to cover it.
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 · 19 lines · 186 tokens per session scan A 339a17dc341a
design is a cursor rule published in the GitHub repository stass/blew (25 stars, last pushed 5mo ago), licensed BSD-2-Clause. It adds 186 tokens to every session, about $0.0007 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
modus-angular-button-group-usage-short
Critical patterns for ModusButton usage inside ModusButtonGroup in Angular.
release-checklist
What to update with each code change or version release.
modus-checkbox-value-inversion-react-short
Critical bug fix for ModusWcCheckbox value property inversion.
pre-flight-check
Mandatory fail-fast quality gate — run Typecheck, Lint, Test, and Security Audit sequentially before declaring any task done or committing code.
05-daemons-ipc
Use this rule to understand the roles of the HAPPE/IDA/mcp-hostd daemons, how HAPPE and IDA communicate via IPC, find the IPC message structure definitions, trace the memory retrieval flow, and identify daemon responsibilities.
graphql
GraphQL: schema design, resolvers, performance.