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/jotjunior/cstk/plannpx skills add JotJunior/cstk --skill plangit clone --depth 1 https://github.com/JotJunior/cstkWrote 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/jotjunior/cstk/plan)<a href="https://agentmods.dev/skills/jotjunior/cstk/plan"><img src="https://agentmods.dev/badge/skills/jotjunior/cstk/plan.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.00115 | $0.04270 |
| Opus 5 | $0.00057 | $0.02135 |
| Sonnet 5 | $0.00023 | $0.00854 |
| Haiku 4.5 | $0.00012 | $0.00427 |
Grade A, and why
plan 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 — 432 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Plano de Implementacao Tecnico
Gere um plano de implementacao completo a partir de uma feature spec, cobrindo arquitetura, decisoes tecnicas, modelo de dados e contratos.
Pre-requisitos
Obrigatorio: docs/specs/{feature}/spec.md ja existente. Sem spec, abortar.
Recomendado:
/clarifyexecutado (reduz NEEDS CLARIFICATION na Etapa 3)docs/constitution.mdexistente (usado como gate — violacoes sao bloqueantes)
Proximos passos
/checklist— gerar quality gate antes de implementar/create-tasks— decompor o plano em backlog executavel/analyze— apos ter tasks, validar consistencia cross-artifact
Argumentos
$ARGUMENTS
Leitura de artefatos foundational (briefing + constitution)
Antes de ler docs/briefing.md (ou o legado
docs/01-briefing-discovery/briefing.md) ou docs/constitution.md
direto do disco, verifique se ha cache valido populado pelo agente-00c
ou feature-00c. Aditivo — se nao houver cache, leia direto do disco
conforme comportamento padrao (FR-CACHE-014).
-
Detectar agente ativo: variavel
AGENTE_00C_STATE_DIRsetada, OU<projeto-alvo>/.claude/agente-00c-state/state.jsonexistente, OU<projeto-alvo>/.claude/feature-00c-state/<short>/state.json. -
Se ativo, tente consumir o resumo via Bash:
~/.claude/skills/agente-00c-runtime/scripts/state-cache.sh get-resumo \ --state-dir "$SD" --artifact briefing- Exit 0 + stdout nao-vazio: use o resumo como conteudo.
- Exit 1: cache miss (campo ausente, estrategia=passthrough, drift detectado) — caia em leitura direta.
- Exit 2: erro fatal (state.json corrompido) — aborte com diagnostico do stderr.
Mesmo protocolo para
--artifact constitution. NOTA: esta skill tem dependencia HARD emdocs/constitution.md(gate de violacoes na ETAPA 2). Se cache miss + arquivo source ausente em disco, isso eh erro de pre-requisito, nao falha do cache. -
Apos consumo (hit ou miss), registre metrica via:
~/.claude/skills/agente-00c-runtime/scripts/state-cache.sh metrics-bump \ --state-dir "$SD" --tipo <hit|miss-drift|miss-disabled> \ [--chars-economizados N]onde N =
source_chars - resumo_charsquando hit, ou 0 caso contrario.
What ships with it
6 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 · 432 lines · 115 tokens per session scan A 99d2b69d4963
plan is a skill published in the GitHub repository JotJunior/cstk (22 stars, last pushed 4d ago), licensed MIT. It adds 115 tokens to every session and 4,270 once invoked, about $0.0006 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…