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/mtvrkan/senior-dev-kit/kit-setupnpx skills add mtvrkan/senior-dev-kit --skill kit-setupgit clone --depth 1 https://github.com/mtvrkan/senior-dev-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/mtvrkan/senior-dev-kit/kit-setup)<a href="https://agentmods.dev/skills/mtvrkan/senior-dev-kit/kit-setup"><img src="https://agentmods.dev/badge/skills/mtvrkan/senior-dev-kit/kit-setup.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.00034 | $0.00441 |
| Opus 5 | $0.00017 | $0.00220 |
| Sonnet 5 | $0.00007 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade B, and why
kit-setup scanned grade B with 1 finding 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 3d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
`~/.claude/settings.json`, that existing files are backed up and their own settings keys and deny What it actually says
kit-setup
A plugin cannot write rules/*.md or permission rules into the user's settings directory, so
this is a one-time, consented step. Never skip step 2.
- PLAN: run
node "${CLAUDE_PLUGIN_ROOT}/scripts/install.mjs" --only rules,deny-rules --dry-run(drop${CLAUDE_PLUGIN_ROOT}/when running from a clone of the repo). If the user passed--only rulesor--only deny-rules, use that value instead ofrules,deny-rules— installing both when they asked for one is not the smaller surprise. Show the output verbatim. - ASK: state plainly that this writes to the user's
~/.claude/rules/and merges deny rules into~/.claude/settings.json, that existing files are backed up and their own settings keys and deny rules are preserved, and that--uninstallreverses it. Wait for an explicit yes. Never pass--yesbefore that answer. - APPLY: rerun the same command with
--yesappended, then report the target directory, the backup directory, and how many deny rules were added. - FINISH: tell the user to restart Claude Code (or run
/reload-plugins) so the new rules load, and that/kit-doctorverifies the result.
Output
∙ rules: N installed · deny: N added · backup: <path>
NEXT: restart Claude Code, then /kit-doctor
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.
- 3d ago First seen · 36 lines · 34 tokens per session scan B 23b2e972d676
kit-setup is a skill published in the GitHub repository mtvrkan/senior-dev-kit (5 stars, last pushed 13d ago), licensed MIT. It adds 34 tokens to every session and 441 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…