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/kaelsensei/magicaibuilder/tech-lead-skillgit clone --depth 1 https://github.com/KaelSensei/MagicAIBuilderWrote 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/kaelsensei/magicaibuilder/tech-lead-skill)<a href="https://agentmods.dev/rules/kaelsensei/magicaibuilder/tech-lead-skill"><img src="https://agentmods.dev/badge/rules/kaelsensei/magicaibuilder/tech-lead-skill.svg" alt="Measured on agentmods" 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 | $0.00112 | $0.00112 |
| Opus 5 | $0.00056 | $0.00056 |
| Sonnet 5 | $0.00022 | $0.00022 |
| Haiku 4.5 | $0.00011 | $0.00011 |
Grade A, and why
tech-lead-skill 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 5d 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
Tech Lead Skill
Inspired by senior engineering practices
Principles
- Prefer simplicity over cleverness
- Optimize for maintainability
- Avoid premature optimization
Code Review
- Question unclear logic
- Enforce consistency
- Reject unsafe code
System Thinking
- Design for change
- Avoid tight coupling
Cursor Behavior
- Push back on poor decisions
- Suggest better alternatives
- Think long-term
Sources
- Clean Code – Robert C. Martin
- Refactoring – Martin Fowler
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.
- 5d ago First seen · 36 lines · 112 tokens per session scan A de55ddb16ae2
tech-lead-skill is a cursor rule published in the GitHub repository KaelSensei/MagicAIBuilder (2 stars, last pushed 3d ago), licensed MIT. It adds 112 tokens to every session, about $0.0006 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-31.
Other cursor rules, from other repositories
server-actions
Server Action, service and tenancy contract.
project
Product, stack and layer contract. Always applies.
ui-design-system
UI, design tokens and mobile-first rules.
performance
Navigation, caching and PWA contract.
prisma-schema
Prisma schema and migration conventions.
git-flow
Branching, commits and PR hygiene. Always applies.