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/fhdumont/code-ai-template/fechar-fasenpx skills add FHDumont/code-ai-template --skill fechar-fasegit clone --depth 1 https://github.com/FHDumont/code-ai-templateWrote 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/fhdumont/code-ai-template/fechar-fase)<a href="https://agentmods.dev/skills/fhdumont/code-ai-template/fechar-fase"><img src="https://agentmods.dev/badge/skills/fhdumont/code-ai-template/fechar-fase.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.1 | $0.00043 | $0.00645 |
| Opus 5 | $0.00022 | $0.00322 |
| Sonnet 5 | $0.00009 | $0.00129 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
fechar-fase 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 — 25 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Checklist do fecho. As regras vivem em AGENTS.md (§Regra de migração, §Git); aqui está a ordem, e onde se para.
Antes da validação do dono
- Rode os critérios de pronto da spec, um por um, com execução real — build, teste, run. Critério que falhou volta pro código; "feito" só depois de verificado.
- Revisão de fecho com contexto fresco. Dispare um subagente via
Taskque não tem o contexto desta sessão e entregue a ele só: os docs vivos, a spec da fase, e o diff (git diff main...HEAD). A pergunta dele é uma: o entregue bate com a intenção da spec, item a item? Divergiu → corrija antes de seguir. Fase que não tocou código pode pular este passo. - Passada única de docs vivos, tudo antes do commit final: spec inteira de
SETUP.md→docs/history/SETUP-HISTORICO.mdcom o bloco Notas de implementação (desvios, soluções não-óbvias, becos evitados — memória, não log); uma linha emdocs/CHANGELOG.md(F-xxx — o que entrou — AAAA-MM-DD); fase removida doROADMAP.md;DEBITO-TECNICO.mdatualizado (débito novo, e o resolvido migrando inteiro pro histórico com nota de como foi); ADR novo se a entrega divergiu por decisão de arquitetura;CONTEXT.mdse a fase afiou algum termo. - Commite a etapa final e pare. Relate ao dono: cada critério com seu resultado, o veredito da revisão de fecho, os docs tocados, e o que ficou de fora e por quê.
O fecho para aqui — PR, merge e limpeza esperam o dono validar. Salvo se o prompt de abertura já autorizou o fecho sem teste; nesse caso siga direto.
Depois de liberado — sem pausar no meio
gh pr createcom corpo curto: o que/por quê, os critérios, e a referência àF-xxx.- Confirme os checks verdes. Um CI por fecho: o build que dispara no merge é entrega, não gate — não espere um segundo.
gh pr merge --rebase— os commits da fase entram lineares nomain, um por etapa.- Apague a branch remota e local, e sincronize:
git switch main && git pull. - Confirme com
git branch: sómain, atualizado com oorigin/main. O dono não toca no GitHub.
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 · 25 lines · 43 tokens per session scan A 01a5393e2692
fechar-fase is a skill published in the GitHub repository FHDumont/code-ai-template (2 stars, last pushed 25d ago), licensed MIT. It adds 43 tokens to every session and 645 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-31.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…