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/cembasaranoglu/crafting-system-claudeWrote 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/cembasaranoglu/crafting-system-claude/40-readiness-gates)<a href="https://agentmods.dev/rules/cembasaranoglu/crafting-system-claude/40-readiness-gates"><img src="https://agentmods.dev/badge/rules/cembasaranoglu/crafting-system-claude/40-readiness-gates/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/cembasaranoglu/crafting-system-claude/40-readiness-gates"><img src="https://agentmods.dev/badge/rules/cembasaranoglu/crafting-system-claude/40-readiness-gates.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.00027 | $0.00108 |
| Opus 5 | $0.00014 | $0.00054 |
| Sonnet 5 | $0.00005 | $0.00022 |
| Haiku 4.5 | $0.00003 | $0.00011 |
Grade A, and why
40-readiness-gates 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
When readiness is discussed, do not answer with a vague yes/no. Use gate statuses: pass, pass_with_risk, partial, fail, blocked, not_applicable, not_assessed. Use evidence levels L0-L5. Never call something production-ready, OSS-ready, secure, deployed, tested, or validated unless source or command evidence proves 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.
- 5d ago First seen · 8 lines · 27 tokens per session scan A 5774a0991d0f
40-readiness-gates is a cursor rule published in the GitHub repository cembasaranoglu/crafting-system-claude (5 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 108 once invoked, about $0.0001 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-09-03.
Other cursor rules, from other repositories
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.
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.