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/TechNickAI/claude_telemetryWrote 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/commands/technickai/claude_telemetry/load-cursor-rules)<a href="https://agentmods.dev/commands/technickai/claude_telemetry/load-cursor-rules"><img src="https://agentmods.dev/badge/commands/technickai/claude_telemetry/load-cursor-rules/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/commands/technickai/claude_telemetry/load-cursor-rules"><img src="https://agentmods.dev/badge/commands/technickai/claude_telemetry/load-cursor-rules.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.00008 | $0.00248 |
| Opus 5.5 | $0.00003 | $0.00099 |
| Sonnet 5.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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- load-rules — 92% identical, 11 lines differ
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.
- 1mo 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 (31 stars, last pushed 11mo ago), licensed MIT. It adds 8 tokens to every session and 248 once invoked, about $0.0000 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-30.
Other commands, from other repositories
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
amp-register
Register your agent with an external AMP provider for cross-provider messaging.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
search
Full-text search the carrel desk index (FTS5, bm25-ranked) for local files matching a query, with type and tag filters.