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/rules/technickai/claude_telemetry/naming-stuff)<a href="https://agentmods.dev/rules/technickai/claude_telemetry/naming-stuff"><img src="https://agentmods.dev/badge/rules/technickai/claude_telemetry/naming-stuff/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/rules/technickai/claude_telemetry/naming-stuff"><img src="https://agentmods.dev/badge/rules/technickai/claude_telemetry/naming-stuff.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.00011 | $0.00276 |
| Opus 5.5 | $0.00004 | $0.00110 |
| Sonnet 5.5 | $0.00002 | $0.00055 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
naming-stuff 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.
What it actually says
Naming Conventions
When in doubt, take time to name things well. It's one of the hardest problems in computer science.
Importance
- Names are a form of documentation that never goes out of date
- Good names reduce cognitive load and make code self-documenting
- Names should reveal intent and provide context
- Time spent on naming is an investment in future understanding
When to Pause and Consider Naming Carefully
The more permanent/harder to change, the more time to spend on naming:
- Creating new models or database tables
- Defining core functions or classes
- Establishing API endpoints or URLs
- Naming background jobs or tasks
- Creating new features or components
- Defining key variables that appear throughout codebase
Notably, don't spend excessive time on naming for simple things that are easy to change.
When Names Aren't Obvious
When a name for a new file, function, class, etc. isn't immediately obvious:
- Pause and ask what we should name it. It's better to ask than to guess and have to rename later.
- Consider multiple alternatives
- Evaluate options based on:
- Clarity and intuitiveness
- Technical accuracy
- Future flexibility
- Project context
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 · 43 lines · 11 tokens per session scan A 0a8eeb6c460e
naming-stuff is a cursor rule published in the GitHub repository TechNickAI/claude_telemetry (31 stars, last pushed 11mo ago), licensed MIT. It adds 11 tokens to every session and 276 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 cursor rules, from other repositories
release-checklist
What to update with each code change or version release.
modus-checkbox-value-inversion-react-short
Critical bug fix for ModusWcCheckbox value property inversion.
pre-flight-check
Mandatory fail-fast quality gate — run Typecheck, Lint, Test, and Security Audit sequentially before declaring any task done or committing code.
05-daemons-ipc
Use this rule to understand the roles of the HAPPE/IDA/mcp-hostd daemons, how HAPPE and IDA communicate via IPC, find the IPC message structure definitions, trace the memory retrieval flow, and identify daemon responsibilities.
graphql
GraphQL: schema design, resolvers, performance.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.