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/stepkar2004/init-configurator/skill-managernpx skills add Stepkar2004/init-configurator --skill skill-managergit clone --depth 1 https://github.com/Stepkar2004/init-configuratorWrote 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/stepkar2004/init-configurator/skill-manager)<a href="https://agentmods.dev/skills/stepkar2004/init-configurator/skill-manager"><img src="https://agentmods.dev/badge/skills/stepkar2004/init-configurator/skill-manager.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.00137 | $0.01176 |
| Opus 5 | $0.00068 | $0.00588 |
| Sonnet 5 | $0.00027 | $0.00235 |
| Haiku 4.5 | $0.00014 | $0.00118 |
Grade A, and why
skill-manager 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 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.
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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
skill-manager — the one skill that is aware of all the others
Individual lessons enter through the evolve procedure, one reviewed diff at a time. Somebody still has to see the whole genome: whether the pieces are at the right altitude, whether gaps and corpses are accumulating. That somebody is this skill, and the periodic pass runs with FRESH context — the writer of a skill never grades it.
Nested-skill architecture (policy, decided 2026-07-11)
- Few top-level skills, lazy references inside. A skill's body is the always-loaded
front door; variants and less-common procedures live in
references/files loaded only when their trigger row matches. Do not rely on separate sibling skills auto-triggering for sub-procedures. - Hard cap: 10 top-level skills; prefer 5-7. At the cap, adding a skill requires
first consolidating two related ones (merge into core + references). Current
top-level set (4):
workflow,skill-manager,socials,bootstrap. - Portability. Embed the external knowledge the genome needs (e.g. authoring
standards in
references/authoring.md) so any coding agent operating this repo has it — never depend on a specific tool's plugin being installed.
The structural rules (load-bearing, not style)
- Skills exist per task-shape, never per incident. A recurring bug becomes one appended procedure in an existing skill, not a new skill.
- Variants of one shape are
references/inside one skill (bootstrap+references/python.md;workflow+references/scale.md), never sibling skills. - Altitude smells: the same diff recurs after a fix → it was patched too low; one edit forces rewriting siblings → it lives too high.
- Bodies stay under ~500 lines (alarm at 150). A bloated skill fails silently — it stops being read carefully. Push volatile detail down into references; push behavioral rules up into CLAUDE.md only when truly session-wide.
- No version numbers in skill bodies. Decision procedures survive years; pins go stale invisibly. Dated observations are allowed in references, marked with their date.
- Authoring standards (descriptions as triggers, progressive disclosure, eval method): references/authoring.md.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 78 lines · 137 tokens per session scan A 206597601b1c
skill-manager is a skill published in the GitHub repository Stepkar2004/init-configurator (1 stars, last pushed 1mo ago), licensed MIT. It adds 137 tokens to every session and 1,176 once invoked, about $0.0007 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 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…