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/muntello/vibe-project-template/_templatenpx skills add Muntello/vibe-project-template --skill _templategit clone --depth 1 https://github.com/Muntello/vibe-project-templateWhat 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.00008 | $0.00428 |
| Opus 5 | $0.00004 | $0.00214 |
| Sonnet 5 | $0.00002 | $0.00086 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
[object Object] 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 2d 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
{{Skill Title}}
One or two sentences on what this covers and, more usefully, what happens to someone who does not know it. Skip the preamble — the agent already decided to read this.
{{The first thing that bites}}
State the mechanic, then the failure it causes:
Deduplication is on
SHA256(raw body), not an event id — the provider sends none. Consequence: two genuinely distinct events with byte-identical bodies collapse into one.
Tables earn their place when there are parallel cases to compare:
| Thing | Where it lives | Gotcha |
|---|---|---|
{{A procedure, if this skill is one}}
Numbered steps, each with the reason it exists. A step whose reason is unstated will be skipped the first time it seems inconvenient.
Deliberate absences
Anything that looks like a gap but is a decision. Without this, someone eventually "fixes" it:
Retention events are intentionally not dispatched — the platform has no native equivalent. Adding one would be a regression, not a gap.
Flags and dark code
Anything that reads as live but runs behind a default-off flag. Name the flag, its default, and what has to be true before flipping it. This is the most reliable way to send someone debugging a bug that does not exist.
Verifying
What actually counts as evidence for this area — a real request, a row in the log table, a query against the running system. Not "the command exited zero".
Guidance for writing this file — ../README.md. No line numbers. No copied business data. No status markers.
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.
- 2d ago First seen · 51 lines · 8 tokens per session scan A 27d13f09a087
[object Object] is a skill published in the GitHub repository Muntello/vibe-project-template (5 stars, last pushed 26d ago), licensed MIT. It adds 8 tokens to every session and 428 once invoked, about $0.0000 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…