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/briefingnpx skills add JotJunior/cstk --skill briefinggit 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/briefing)<a href="https://agentmods.dev/skills/jotjunior/cstk/briefing"><img src="https://agentmods.dev/badge/skills/jotjunior/cstk/briefing.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.00049 | $0.03755 |
| Opus 5 | $0.00024 | $0.01878 |
| Sonnet 5 | $0.00010 | $0.00751 |
| Haiku 4.5 | $0.00005 | $0.00376 |
Grade A, and why
briefing 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 5d 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 — 404 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Briefing de Projeto
Conduza uma entrevista estruturada de discovery para capturar a essencia do projeto, produzindo um documento de briefing que serve de fundacao para todos os artefatos SDD.
Pre-requisitos
Nenhum. Esta e tipicamente a primeira skill do pipeline SDD para novos projetos. Se ja existe um briefing, esta skill pode atualiza-lo.
Proximos passos
Apos salvar o briefing, o fluxo sugerido e:
/constitution— derivar principios de governanca a partir do briefing/specify— especificar as features do MVP identificadas no briefing
Argumentos
$ARGUMENTS
FLUXO DE EXECUCAO
1. CONTEXTO Detectar projeto e artefatos existentes
|
2. TRIAGEM Determinar profundidade da entrevista
|
3. ENTREVISTA Perguntas estruturadas por dimensao (interativo)
|
4. SINTESE Consolidar respostas em documento de briefing
|
5. VALIDACAO Confirmar com usuario antes de salvar
|
6. SALVAMENTO Salvar e recomendar proximos passos
ETAPA 1: CONTEXTO
1.1 Detectar Projeto
Leia os seguintes arquivos (se existirem) para entender o que ja se sabe:
SEMPRE LER (se existirem):
-- README.md
-- CLAUDE.md
-- docs/briefing.md (briefing atual, caminho canonico)
-- docs/01-briefing-discovery/*.md (briefings legados)
-- docs/constitution.md
-- docs/specs/*/spec.md (specs existentes)
-- package.json, go.mod, pyproject.toml, Cargo.toml (stack tecnica)
1.2 Verificar Briefing Existente
Procurar briefings existentes (canonico primeiro, legado depois):
docs/briefing.md(caminho canonico)docs/01-briefing-discovery/briefing.md(legado)docs/01-briefing-discovery/BRIEFING-*.md(legado)
Se encontrado:
- Carregar conteudo atual
- Identificar secoes incompletas ou marcadas com TODO
- Perguntar ao usuario: "Encontrei um briefing existente. Deseja atualizar ou criar um novo?"
- Se encontrado APENAS no caminho legado: registrar que o salvamento continuara no caminho legado (ver Etapa 6.2) — nunca mover o arquivo sem o usuario pedir
What ships with it
3 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.
- 5d ago First seen · 404 lines · 49 tokens per session scan A 334a44f7f5d4
briefing is a skill published in the GitHub repository JotJunior/cstk (23 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 3,755 once invoked, about $0.0002 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.
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…
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…