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/checklist)<a href="https://agentmods.dev/commands/felvieira/claude-skills-fv/checklist"><img src="https://agentmods.dev/badge/commands/felvieira/claude-skills-fv/checklist/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/checklist"><img src="https://agentmods.dev/badge/commands/felvieira/claude-skills-fv/checklist.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.01868 |
| Opus 5 | $0.00014 | $0.00934 |
| Sonnet 5 | $0.00005 | $0.00374 |
| Haiku 4.5 | $0.00003 | $0.00187 |
Grade A, and why
checklist 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 12d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/checklist — Unit Tests for English
Objetivo: gerar checklist específica por feature que valida a qualidade dos requisitos, não da implementação. Pense em "unit tests para a spec escrita em inglês/português".
Complementa policies/prd-validation.md (que tem 13 checks fixos). Aqui são checks derivados da própria spec — específicos para o domínio dela.
Inspirado em github/spec-kit — /speckit.checklist.
Conceito-chave
É:
- ✅ "Os requisitos de hierarquia visual estão definidos para todos os tipos de card?" (completeness)
- ✅ "'Display proeminente' está quantificado com tamanho/posição específicos?" (clarity)
- ✅ "Estado de hover está consistente entre todos os elementos interativos?" (consistency)
- ✅ "Requisitos de acessibilidade estão definidos para navegação por teclado?" (coverage)
- ✅ "A spec define o que acontece quando a imagem do logo falha?" (edge cases)
NÃO é:
- ❌ "Verificar se o botão clica corretamente" (isso é teste de implementação)
- ❌ "Testar tratamento de erro funciona"
- ❌ "Confirmar API retorna 200"
Se a spec é "código escrito em inglês", esta checklist é a suíte de testes unitários dela.
Quando usar
- depois de
/specou/to-prd, antes de/plan - depois de
/grill-mepara auditar se a discovery cobriu tudo - antes de
/analyze(que cruza artefatos) —/checklisté por-feature,/analyzeé cross-artifact - ao revisar PR que muda uma spec existente
Quando NÃO usar
- spec ainda vaga → rode
/grill-meantes - bug fix isolado (sem spec formal)
- iteração mecânica (rename, format)
Processo
1. Ler spec alvo
Detectar:
# preferência: argumento explícito
SPEC="${1:-}"
# fallback: spec mais recente em docs/specs/
[ -z "$SPEC" ] && SPEC=$(ls -t docs/specs/*.md 2>/dev/null | head -1)
# fallback 2: PRD do Taskmaster
[ -z "$SPEC" ] && [ -f ".taskmaster/docs/prd.md" ] && SPEC=".taskmaster/docs/prd.md"
[ -z "$SPEC" ] && { echo "ERRO: nenhuma spec encontrada"; exit 2; }
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.
- 12d ago First seen · 192 lines · 27 tokens per session scan A 2491cd30b706
checklist 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,868 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.