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/clarifynpx skills add JotJunior/cstk --skill clarifygit 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/clarify)<a href="https://agentmods.dev/skills/jotjunior/cstk/clarify"><img src="https://agentmods.dev/badge/skills/jotjunior/cstk/clarify.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.00052 | $0.04148 |
| Opus 5 | $0.00026 | $0.02074 |
| Sonnet 5 | $0.00010 | $0.00830 |
| Haiku 4.5 | $0.00005 | $0.00415 |
Grade A, and why
clarify 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 4d 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 — 440 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Clarificar Spec
Identifique e resolva ambiguidades em uma feature spec existente via perguntas estruturadas, integrando as respostas diretamente no documento.
Modos de invocacao
Esta skill suporta dois modos:
-
Interativo (default) — humano executa
/clarify; skill faz Q&A direto com o usuario, uma pergunta por vez (ETAPA 4 deste documento). -
Padrao de dois atores (apenas dentro de
agente-00c) — o orquestrador spawnaagente-00c-clarify-asker(gera perguntas) +agente-00c-clarify-answerer(responde com scoring 0..3) como subagentes irmaos. NAO chame esses subagentes diretamente via/clarify— eles sao primitivas do orquestrador.Dentro do modo dois-atores, se a tool Agent estiver indisponivel no harness (sintoma: spawn falha com erro de tool, nao com erro de prompt), o orquestrador faz downgrade EXPLICITO via Decisao auditada — nao silently fallback. Ver
agente-00c-orchestrator.md§5.a (Dry-run da tool Agent).
Pre-requisitos
Obrigatorio: spec.md ja existente (criado via /specify ou manualmente).
Sem spec, a skill aborta e instrui a rodar /specify primeiro.
Opcional: docs/constitution.md para validar respostas contra principios.
Proximos passos
/checklist— gerar quality gate de requisitos apos clarificacao/plan— spec agora esta pronta para gerar plano tecnico/clarifynovamente — apenas se Outstanding de alto impacto persistirem
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.
What ships with it
1 file 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.
- 4d ago First seen · 440 lines · 52 tokens per session scan A 6dd213d5e180
clarify is a skill published in the GitHub repository JotJunior/cstk (22 stars, last pushed 4d ago), licensed MIT. It adds 52 tokens to every session and 4,148 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…