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 skills add lucasandradeb/my-claude-code-config --skill spec-drivengit clone --depth 1 https://github.com/lucasandradeb/my-claude-code-configWrote 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/lucasandradeb/my-claude-code-config/spec-driven)<a href="https://agentmods.dev/skills/lucasandradeb/my-claude-code-config/spec-driven"><img src="https://agentmods.dev/badge/skills/lucasandradeb/my-claude-code-config/spec-driven/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/lucasandradeb/my-claude-code-config/spec-driven"><img src="https://agentmods.dev/badge/skills/lucasandradeb/my-claude-code-config/spec-driven.svg" alt="Reviewed on agentmods" width="80" 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.00038 | $0.01067 |
| Opus 5.5 | $0.00015 | $0.00427 |
| Sonnet 5.5 | $0.00008 | $0.00213 |
| Haiku 4.5 | $0.00004 | $0.00107 |
Grade B, and why
spec-driven scanned grade B with 2 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 2mo 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
curl -X POST http://localhost:3000/endpoint -d '{"key":"value"}' Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST http://localhost:3000/endpoint -d '{"key":"value"}' How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-Driven Development Setup
Overview
Spec-driven development transforma requisitos vagos em artefatos estruturados que o Claude pode usar para verificar o proprio trabalho. O ciclo e: escrever spec → implementar → validar contra criterios de aceite.
Principio central: Uma boa spec nao descreve apenas "o que construir", mas tambem "como saber que esta correto".
Quando Usar
- Novo projeto iniciando do zero
- Nova feature com escopo nao trivial
- Qualquer entrega onde "feito" precisa de definicao objetiva
Passo 1 — Setup da Estrutura
Se o projeto nao tem a estrutura abaixo, criá-la agora:
projeto/
├─ CLAUDE.md # convencoes permanentes (stack, build, lint, test)
├─ docs/
│ └─ specs/
│ └─ .gitkeep
└─ .claude/
└─ settings.json
mkdir -p docs/specs .claude
touch docs/specs/.gitkeep
Se CLAUDE.md nao existir, perguntar ao usuario:
- Stack principal e versoes
- Comando de build/test/lint
- Padroes de PR e commit
- Restricoes de arquitetura
Passo 2 — Criar a Spec
Criar docs/specs/<nome-da-feature>.md com o template abaixo.
Preencher cada secao com o usuario antes de qualquer codigo.
# [Nome da Feature]
## Problema
<!-- O que esta quebrado ou faltando? Por que isso importa? -->
## Objetivo
<!-- Uma frase: o que deve ser verdade apos a implementacao? -->
## Escopo
### Incluido
-
### Excluido (fora de escopo)
-
## Requisitos Funcionais
<!-- O que o sistema DEVE fazer -->
1.
## Requisitos Nao Funcionais
<!-- Performance, seguranca, compatibilidade -->
-
## Criterios de Aceite
<!-- Condicoes objetivas e verificaveis. Cada item deve ser true/false. -->
- [ ]
- [ ]
## Validacao
<!-- Comandos exatos para verificar cada criterio de aceite -->
```bash
# exemplo:
npm test -- --testPathPattern=feature-x
curl -X POST http://localhost:3000/endpoint -d '{"key":"value"}'
Arquivos Impactados
Dependencias e Riscos
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.
- 2mo ago First seen · 149 lines · 38 tokens per session scan B 5e6fbc548ef2
spec-driven is a skill published in the GitHub repository lucasandradeb/my-claude-code-config (2 stars, last pushed 24d ago), licensed MIT. It adds 38 tokens to every session and 1,067 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…