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/igoruehara/spec-driven/evalsnpx skills add igoruehara/spec-driven --skill evalsgit clone --depth 1 https://github.com/igoruehara/spec-drivenWhat 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.00055 | $0.00363 |
| Opus 5 | $0.00028 | $0.00181 |
| Sonnet 5 | $0.00011 | $0.00073 |
| Haiku 4.5 | $0.00006 | $0.00036 |
Grade A, and why
evals 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.
What it actually says
Skill: Evals de fidelidade spec→código
Mede se o que foi construído reflete a spec — a métrica de qualidade da saída do agente. Duas camadas: determinística (script) e de julgamento.
1. Camada determinística
node scripts/eval-spec-fidelity.mjs .
Reporta, por feature: AC totais, cobertos por task, referenciados em teste/código e SPEC_DEVIATION abertos. Falha (exit 1) se algum AC não tem task — rastreabilidade quebrada. Referência em teste é aviso até a feature ser implementada.
2. Camada de julgamento (o script não pega isso)
- O teste de cada
AC-Nrealmente exercita o Given/When/Then — ou só cita o ID num teste vazio? - A implementação cobre os casos de borda e respeitou o "Fora de escopo" da spec?
- Os
SPEC_DEVIATIONabertos têm resolução (corrigir código ou atualizar a spec/ADR)?
Saída
Score por feature + os gaps. Complementa o /validar (UAT de uma feature) com uma visão de
fidelidade do portfólio. O mesmo eval roda na CI (esteira.yml) — aqui é o complemento com julgamento.
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 · 27 lines · 55 tokens per session scan A d755c86570b3
evals is a skill published in the GitHub repository igoruehara/spec-driven (213 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 363 once invoked, about $0.0003 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
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…