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 skills/sunnypatneedi/claude-starter-kit/performance-optimizationnpx skills add sunnypatneedi/claude-starter-kit --skill performance-optimizationgit clone --depth 1 https://github.com/sunnypatneedi/claude-starter-kitWrote 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/skills/sunnypatneedi/claude-starter-kit/performance-optimization)<a href="https://agentmods.dev/skills/sunnypatneedi/claude-starter-kit/performance-optimization"><img src="https://agentmods.dev/badge/skills/sunnypatneedi/claude-starter-kit/performance-optimization.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.1 | $0.00033 | $0.02734 |
| Opus 5 | $0.00016 | $0.01367 |
| Sonnet 5 | $0.00007 | $0.00547 |
| Haiku 4.5 | $0.00003 | $0.00273 |
Grade A, and why
performance-optimization 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 459 lines · 33 tokens per session scan A 75ec5dad72ef
performance-optimization is a skill published in the GitHub repository sunnypatneedi/claude-starter-kit (11 stars, last pushed 6mo ago), with no licence file. It adds 33 tokens to every session and 2,734 once invoked, about $0.0002 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 skills, from other repositories
goal-setup
Use on iteration 0 of any /goal — when a goal has just been set, when GOAL.md exists without PHASES.md, or when a goal's phase decomposition must be rebuilt after a re-scope ruling.
handoff
Use when ending a work session that changed project state, when the user says "facciamo il punto"/"a che punto siamo"/"riprendiamo", when starting work in a project that has a HANDOFF.md, or after a crash/context loss when prior session state must be reconstructed.
done
Use when about to claim a task is complete, fixed, implemented, or ready to merge/deploy/push — and when the user asks "fatto?", "finito?", "possiamo mergiare?", or "quanto rischio a pushare?". Use before ending any session or loop iteration that changed code.
peripheral-vision
Use at the end of substantive coding, debugging, or exploration work — before the completion report — and whenever the user asks "c'è altro che dovrei sapere?" or requests a risk scan of recent changes.
spec-first
Use when starting any feature or product slice expected to take more than a session — when the user describes something to build ("facciamo", "creiamo", "voglio una pagina/feature"), before implementation planning, or when a goal phase lacks a written spec.
loop-iteration
Use at the start of every /loop iteration and every /goal work cycle — when resuming autonomous work from a schedule wake-up, when a loop prompt says "continue the loop / continua il loop", or when about to schedule the next iteration of long-horizon work.