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/kabi10/cursor-rules/checklistgit clone --depth 1 https://github.com/Kabi10/cursor-rulesWhat 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.00432 | $0.00432 |
| Opus 5 | $0.00216 | $0.00216 |
| Sonnet 5 | $0.00086 | $0.00086 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
checklist 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 2d 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
Pre-Implementation Checklist
🔍 MANDATORY: Search First
Before making ANY changes or implementing ANY new features:
-
Search Existing Code
# Document ALL search results grep_search "[feature keyword]" # Search for related functionality file_search "[filename pattern]" # Search for similar files list_dir "[relevant directory]" # List contents of directories -
Document Findings
## Existing Files Found: - [List all relevant files with full paths] - [Include file sizes and last modified dates] ## Existing Functionality: - [Describe what already exists] - [Note patterns and approaches used] ## Gaps Identified: - [List what's missing] - [Note technical debt] ## Implementation Decision Tree: - Is there existing code that serves this purpose? [Yes/No] - Can existing code be enhanced? [Yes/No] - Is creating new code justified? [Yes/No + reasoning] -
✋ Wait for Approval
- Present findings with clear options
- Get explicit approval for approach
- Never proceed with new files if similar exists
- Document approval in implementation plan
Examples
Critical Rules
- NEVER skip the search phase
- ALWAYS document findings before proceeding
- Get explicit approval for approach
- Use existing code when possible
- Document decisions and reasoning description: globs: alwaysApply: false
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.
- 2d ago First seen · 69 lines · 432 tokens per session scan A 35c98d20b8c9
checklist is a cursor rule published in the GitHub repository Kabi10/cursor-rules (21 stars, last pushed 2mo ago), licensed MIT. It adds 432 tokens to every session, about $0.0022 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-08-30.
Other cursor rules, from other repositories
project-rules
Cursor rule "project-rules" from peva3/anchor, covering cursor ai rules, core directives, critical enforcements, pre-commit checklist and required folders.
general
Cursor rule "general" from maxgfr/conforme, covering claude.md, project overview, build & test, architecture and keeping docs in sync.
cursor-project-rule
Project Spine operating contract for "Ledger API".
project-spine-apps-web
Project Spine scoped guidance for "apps/web".
project-spine-packages-ui
Project Spine scoped guidance for "packages/ui".
adapter-consistency
adapter-consistency.