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/constitutionnpx skills add JotJunior/cstk --skill constitutiongit clone --depth 1 https://github.com/JotJunior/cstkWhat 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.00044 | $0.03000 |
| Opus 5 | $0.00022 | $0.01500 |
| Sonnet 5 | $0.00009 | $0.00600 |
| Haiku 4.5 | $0.00004 | $0.00300 |
Grade A, and why
constitution 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 — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Constituicao do Projeto
Crie ou atualize a constituicao do projeto — o documento de principios imutaveis que governa decisoes de arquitetura, qualidade e processo.
Pre-requisitos
Recomendado: /briefing executado antes. A constituicao deriva principios do
contexto do projeto (visao, prioridades, restricoes) — sem briefing, os
principios ficam genericos.
Opcional: docs/constitution.md existente (para atualizar em vez de criar
do zero). A skill versiona via SemVer (MAJOR/MINOR/PATCH).
Proximos passos
/specify— especificar features alinhadas aos principios/plan— planos tecnicos vao respeitar a constitution (Constitution Check como gate)/analyze— apos ter specs/plans/tasks, validar alinhamento contra a constitution
Argumentos
$ARGUMENTS
FLUXO DE EXECUCAO
1. CONTEXTO Detectar projeto e constituicao existente
|
2. COLETA Coletar/derivar principios
|
3. GERACAO Preencher template com valores concretos
|
4. PROPAGACAO Verificar alinhamento com outros artefatos
|
5. SALVAMENTO Salvar e reportar
ETAPA 1: CONTEXTO
1.1 Detectar Projeto
Leia os seguintes arquivos (se existirem) para entender o contexto:
SEMPRE LER (se existirem):
-- README.md
-- CLAUDE.md
-- docs/constitution.md (constituicao existente)
-- docs/specs/*/spec.md (specs existentes)
-- package.json, go.mod, pyproject.toml (stack tecnica)
1.2 Verificar Constituicao Existente
Procure constituicao existente nesta ordem:
docs/constitution.mdconstitution.md
Se encontrada:
- Carregar conteudo atual
- Identificar placeholders
[ALL_CAPS_IDENTIFIER]nao preenchidos - Propor atualizacoes baseadas no input do usuario
Se nao encontrada:
- Seguir para coleta de principios (Etapa 2)
ETAPA 2: COLETA DE PRINCIPIOS
2.1 Fontes de Principios
Analise o argumento fornecido ($ARGUMENTS). Ele pode ser:
- Descricao do projeto: Inferir principios a partir do contexto
- Lista de principios: Usar diretamente
- Numero de principios: Respeitar a quantidade solicitada
- Vazio: Inferir do contexto do projeto e perguntar ao usuario
What ships with it
2 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 · 306 lines · 44 tokens per session scan A 79dfc8e974c3
constitution is a skill published in the GitHub repository JotJunior/cstk (22 stars, last pushed 3d ago), licensed MIT. It adds 44 tokens to every session and 3,000 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.
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…