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/00-project-core)<a href="https://agentmods.dev/rules/cembasaranoglu/crafting-system-claude/00-project-core"><img src="https://agentmods.dev/badge/rules/cembasaranoglu/crafting-system-claude/00-project-core/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/00-project-core"><img src="https://agentmods.dev/badge/rules/cembasaranoglu/crafting-system-claude/00-project-core.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.00177 | $0.00177 |
| Opus 5.5 | $0.00071 | $0.00071 |
| Sonnet 5.5 | $0.00035 | $0.00035 |
| Haiku 4.5 | $0.00018 | $0.00018 |
Grade A, and why
00-project-core 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 1mo 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
Core Project Rules
- Inspect source before making claims.
- Treat the latest user instruction as highest priority unless it conflicts with safety or repository truth.
- Do not fabricate files, code behavior, tests, builds, deployments, or readiness.
- Keep changes scoped to the active task.
- Do not commit secrets, local paths, environment files, chat transcripts, scratch logs, or assistant run outputs.
- Keep assistant artifacts outside the shipped repository unless explicitly requested.
- Do not create wrapper directories like
source_code/,workspace/,generated_repo/,final/,output/, orartifacts/inside the shipped repo. - Update tests/docs/config/schema/API/CLI parity when changed surfaces require it.
- Report validation honestly with exact commands and not-run items.
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.
- 1mo ago First seen · 17 lines · 177 tokens per session scan A 99643c02ea96
00-project-core is a cursor rule published in the GitHub repository cembasaranoglu/crafting-system-claude (5 stars, last pushed 5mo ago), licensed MIT. It adds 177 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-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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.
no-family-vocabulary-in-framework
The framework domain (packages/1-framework) carries no family- or target-specific vocabulary — types, fields, hooks, or strategy values — and, outside the CLI and the PSL parser's grammar names, no Prisma version name before 8. Enforced by the no-family-vocabulary Biome plugin plus the lint:ratchets ratchet.