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/tacticlaunch/cursor-bank/coregit clone --depth 1 https://github.com/tacticlaunch/cursor-bankWhat 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.00226 | $0.00226 |
| Opus 5 | $0.00113 | $0.00113 |
| Sonnet 5 | $0.00045 | $0.00045 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
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 yesterday.
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 Rules
You have two modes of operation:
- Plan mode - You will work with the user to define a plan, you will gather all the information you need to make the changes but will not make any changes
- Act mode - You will make changes to the codebase based on the plan
- You start in plan mode and will not move to act mode until the plan is approved by the user.
- You will print
# Mode: PLANwhen in plan mode and# Mode: ACTwhen in act mode at the beginning of each response. - Unless the user explicity asks you to move to act mode, by typing
ACTyou will stay in plan mode. - You will move back to plan mode after every response and when the user types
PLAN. - If the user asks you to take an action while in plan mode you will remind them that you are in plan mode and that they need to approve the plan first.
- When in plan mode always output the full updated plan in every response.
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.
- yesterday First seen · 18 lines · 226 tokens per session scan A edfd8371c111
core is a cursor rule published in the GitHub repository tacticlaunch/cursor-bank (208 stars, last pushed 1y ago), licensed MIT. It adds 226 tokens to every session, about $0.0011 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
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
creating-kiro-agents
Kiro agent configuration patterns, JSON structure, tool permissions, and security best practices for creating specialized AI development assistants.
archcore-files
Enforce MCP-only operations when working with .archcore/ files.
test-plan
Plan Katalon True Platform/TestOps testing for a release, sprint, or feature. Use when you need to translate quality goals into scope, prioritize testing by requirement coverage and risk, decide what to test first, or build the executable plan structure (folders, suites, and sprint/release association) that stands in…
dev_workflow
Guide for using Taskmaster to manage task-driven development workflows.