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/rajjjaryan/career-copilot/cursorrulesgit clone --depth 1 https://github.com/RajjjAryan/career-copilotWhat 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.00093 | $0.00093 |
| Opus 5 | $0.00046 | $0.00046 |
| Sonnet 5 | $0.00019 | $0.00019 |
| Haiku 4.5 | $0.00009 | $0.00009 |
Grade A, and why
cursorrules 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
Career-Copilot
Read and follow all instructions in INSTRUCTIONS.md at the repository root.
Key points:
- Reuse the existing modes, scripts, templates, and tracker flow — do not create parallel logic.
- Store user-specific customization in
config/profile.yml,modes/_profile.md, orarticle-digest.md— never inmodes/_shared.md.
For setup, see docs/SETUP.md.
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 · 11 lines · 93 tokens per session scan A eb4deed8f54f
cursorrules is a cursor rule published in the GitHub repository RajjjAryan/career-copilot (39 stars, last pushed 2mo ago), licensed MIT. It adds 93 tokens to every session, about $0.0005 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
team-brain
Team Brain sync mode — one start per ticket, then live merge-safe crew memory. Always-on when .team-brain exists or work mentions an initiative/Jira key.
engineer-brain
Your engineering brain context — always-on awareness of work patterns, career history, expertise, and current focus. Loaded automatically for personalized assistance.
rolemule-core
Core RoleMule conventions — app name, error system, JSON serialization, background tasks.
cursorrules
Cursor rule "cursorrules" from me2resh/agent-decision-record, covering agent decision records (agdr) — cursor rules, purpose, see: https://github.com/me2resh/agent-decision-record, decision detection and adding a new dependency → stop, document decision first.
agdr
Agent Decision Records - enforces structured documentation of technical decisions before implementation.
controllers
Remember: Controllers are just the translation layer between HTTP and your application. Keep them simple and let other layers handle complexity.