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.
git clone --depth 1 https://github.com/felvieira/claude-skills-fvWrote 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/commands/felvieira/claude-skills-fv/constitution)<a href="https://agentmods.dev/commands/felvieira/claude-skills-fv/constitution"><img src="https://agentmods.dev/badge/commands/felvieira/claude-skills-fv/constitution/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/commands/felvieira/claude-skills-fv/constitution"><img src="https://agentmods.dev/badge/commands/felvieira/claude-skills-fv/constitution.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.00027 | $0.01224 |
| Opus 5 | $0.00014 | $0.00612 |
| Sonnet 5 | $0.00005 | $0.00245 |
| Haiku 4.5 | $0.00003 | $0.00122 |
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 11d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/constitution — Princípios Governantes do Projeto
Objetivo: criar/atualizar memory/constitution.md no repo consumidor. Os 5 eixos da constituição (Code Quality, Testing, UX, Performance, Security) viram fonte canônica que /spec, /plan, /build, /review e /ship consultam.
Quando usar:
- bootstrap de projeto novo (depois de
/setup//repo-audit) - mudança organizacional (novo framework de compliance, novo budget de custo)
- onboarding de skills do kit num projeto existente sem princípios formais
Quando NÃO usar:
- ajuste micro de um princípio existente → editar
memory/constitution.mddireto + commitchore(constitution): ... - decisão arquitetural localizada → vai pra
docs/adr/não pra constituição
Skill ativada: PO (skill 01) em modo "governance authoring".
Pré-requisitos:
- repo audit feito (
docs/repo-audit/current.md) — pra detectar stack e propor defaults sensatos - glossário (
docs/glossary.mdouCONTEXT.md) opcional, usado pra naming
Processo
Passo 1 — Detectar estado atual
# Existe constituição?
test -f memory/constitution.md && echo "EXISTE" || echo "AUSENTE"
- Existe: modo
update—AskUserQuestionoferece: Review / Add principle / Modify principle / Bump version / Cancel - Ausente: modo
bootstrap— segue para passo 2
Passo 2 — Discovery por eixo (5 mini-entrevistas)
Para cada eixo, perguntar 2-4 perguntas com defaults baseados no repo audit (não pergunte stack se package.json mostra; não pergunte se TDD existe se há testes).
Eixo 1 — Code Quality:
- Linter e formatter atuais? (deduzir de
.eslintrc,pyproject.toml, etc.) - Limite de complexidade ciclomática aceitável?
- Linguagens proibidas no projeto?
Eixo 2 — Testing Standards:
- TDD obrigatório / opcional / por módulo crítico?
- Coverage mínimo aceitável?
- Como tratar flaky tests?
Eixo 3 — UX Consistency:
- Design system existente? Qual?
- WCAG nível mínimo?
- Locales obrigatórios?
- Performance percebida budgets (LCP/INP/CLS)?
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.
- 11d ago First seen · 123 lines · 27 tokens per session scan A 96ed4e167f45
constitution is a command published in the GitHub repository felvieira/claude-skills-fv (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 27 tokens to every session and 1,224 once invoked, about $0.0001 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 commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
music-suno-prompt
Grounded Suno prompt synthesis from local knowledge corpus + persona canon + label canon. No vibes-prompting.