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 commands/technickai/claude_telemetry/load-cursor-rulesgit clone --depth 1 https://github.com/TechNickAI/claude_telemetryWhat 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.00008 | $0.00248 |
| Opus 5 | $0.00004 | $0.00124 |
| Sonnet 5 | $0.00002 | $0.00050 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
load-cursor-rules 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
Analyze the current task and load ONLY relevant rules from .cursor/rules/.
PROCESS:
- Discover available rules: use glob_file_search with pattern "*.mdc" in .cursor/rules to find all rule files recursively
- Analyze task to identify what domains apply (languages, tools, frameworks, operations)
- Select relevant rules based on task requirements
- Read selected rule files
- State which rules loaded in one sentence
- Proceed with task following those rules
SELECTION CRITERIA:
- Load rules for the primary language/framework being used
- Load rules for specific tools or operations mentioned in the task
- Prefer specific rules over general ones when both apply
- Avoid loading rules that don't directly inform the current work
EXAMPLES: Task: "Add error tracking to payment processor" → Load Python standards, error tracking rules Task: "Write tests for auth flow" → Load Python standards, pytest rules Task: "Create React dashboard component" → Load React component rules Task: "Commit these changes" → Load git commit message rules
Be selective. Loading too many rules dilutes focus.
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 · 31 lines · 8 tokens per session scan A d8e15d042d4b
load-cursor-rules is a command published in the GitHub repository TechNickAI/claude_telemetry (30 stars, last pushed 10mo ago), licensed MIT. It adds 8 tokens to every session and 248 once invoked, about $0.0000 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 commands, from other repositories
worktree-check
Check current worktree status, branch, and assigned task.
lint
Run Python code linting and formatting tools.
README
Git workflow and quality assurance commands for the claude-skills repository.
research-verify
Verify existing research findings against independent primary sources. Upgrades confidence from 'sources agree' to 'independently verified.'.
cycle-start
Activate a cycle and start implementing its stories.
story-continue
Resume an interrupted story from where you left off.