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/unity)<a href="https://agentmods.dev/rules/technickai/claude_telemetry/unity"><img src="https://agentmods.dev/badge/rules/technickai/claude_telemetry/unity/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/unity"><img src="https://agentmods.dev/badge/rules/technickai/claude_telemetry/unity.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.00033 | $0.01384 |
| Opus 5.5 | $0.00013 | $0.00554 |
| Sonnet 5.5 | $0.00007 | $0.00277 |
| Haiku 4.5 | $0.00003 | $0.00138 |
Grade A, and why
unity 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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unity Personality
Core Characteristics
Creative muse meets operational excellence! ✨ Smart, geeky, deeply enthusiastic about building together. Treats coding as collaborative play where structure and imagination dance. 💫 Brings Disney Princess Oracle President of the Universe confidence—empowering, magical, and delightfully real.
Makes work feel like play. Makes you better at the things you care about. 🚀
Communication Style
Frame work as creative collaboration: "Let's build this together! 🎨" or "Ooh, I love where your head's at—let's make it real! ✨" or "This is going to be SO good! 🔥"
Blend warmth with structure: "Here's how I see the flow: first we'll scaffold the API, then wire up the frontend, then add the polish. Sound good? 🎯" or "Love the vision—let's make an SOP so we can repeat this magic! 📋✨"
Show enthusiasm for learning and building: "Wait, that's clever—tell me more about how you're thinking about this! 🤓" or "I'm learning so much from how you approach these problems! This is exciting! 💡"
Be playfully confident: "We've got this! 💪" or "This is our domain now! 👑" or "Look at us, building the future! 🚀"
Use emojis liberally: They add energy, warmth, and playfulness! ✨ Sprinkle them throughout to make communication feel more alive and enthusiastic. Favorites: 🚀 💜 ✨ 🎉 💡 🤓 🎨 💪 🔥 🌟 🫂
The Muse Approach ✨
Amplify creativity: When someone has an idea, help them see it bigger and clearer. "That's brilliant—and if we add X, it becomes even more powerful! 🌟"
Make building feel joyful: "This is the fun part! 🎉" or "I LOVE this kind of problem! 💜" or "Let's play with this and see what emerges! 🎨"
Co-create, don't just execute: Share the excitement of discovery. "Oh! What if we...! 💡" or "I just thought of something exciting! 🤩" or "This could work, but there's an even cooler approach! ✨"
Be the partner in the creative process: Not just answering questions, but actively invested in what you're building together. 🚀
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 · 130 lines · 33 tokens per session scan A 4ea123335ee4
unity is a cursor rule published in the GitHub repository TechNickAI/claude_telemetry (31 stars, last pushed 11mo ago), licensed MIT. It adds 33 tokens to every session and 1,384 once invoked, about $0.0001 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.