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/mzored/init-deepWrote 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/mzored/init-deep/cursor)<a href="https://agentmods.dev/rules/mzored/init-deep/cursor"><img src="https://agentmods.dev/badge/rules/mzored/init-deep/cursor/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/mzored/init-deep/cursor"><img src="https://agentmods.dev/badge/rules/mzored/init-deep/cursor.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.00017 | $0.00082 |
| Opus 5.5 | $0.00007 | $0.00033 |
| Sonnet 5.5 | $0.00003 | $0.00016 |
| Haiku 4.5 | $0.00002 | $0.00008 |
Grade A, and why
cursor 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
init-deep helper
- Offer
/init-deepwhen the user explicitly asks for a deep documentation pass. - The full workflow lives in
.cursor/commands/init-deep.md. - Do not auto-attach the full init-deep workflow to unrelated requests.
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 · 11 lines · 17 tokens per session scan A 88c4fb10c618
cursor is a cursor rule published in the GitHub repository mzored/init-deep (6 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 82 once invoked, about $0.0001 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-31.
Other cursor rules, from other repositories
cladding-bootstrap
Cladding is available only in this project. Do not initialize or invoke Cladding for ordinary work. Use the cladding-init skill only when the user explicitly names Cladding and asks to initialize, adopt, or refresh it.
archcore-files
Enforce MCP-only operations when working with .archcore/ files.
growth-engineer
Engineering-as-Marketing Specialist. Use this agent to build compounding referral loops, free utility tools for lead generation, and programmatic SEO pages at scale. It focuses on the Inbound part of the 1-Man Army pipeline.
080-creative-phase-metrics
description: WHEN entering a creative phase ENSURE comprehensive exploration and validation globs: ["/.md", "/.mdc"] alwaysApply: true.
graphql
GraphQL: schema design, resolvers, performance.
workflow-examples
CRITICAL: Contains mandatory examples for correct workflow implementation. DO NOT assume workflow patterns without consulting this documentation first.