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/PedroHenrique0713/brain-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/commands/pedrohenrique0713/brain-template/vault_gc)<a href="https://agentmods.dev/commands/pedrohenrique0713/brain-template/vault_gc"><img src="https://agentmods.dev/badge/commands/pedrohenrique0713/brain-template/vault_gc.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.00027 | $0.00409 |
| Opus 5 | $0.00014 | $0.00204 |
| Sonnet 5 | $0.00005 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
vault_gc 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 6d 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.
What it actually says
vault_gc
Use semanalmente ou quando o vault estiver acumulando lixo operacional.
Escopo
07 - HANDOVERS/: mover handovers finalizados ou antigos para07 - HANDOVERS/Arquivo/.07 - HANDOVERS/Tarefas/: mover tarefas finalizadas para07 - HANDOVERS/Tarefas/Arquivo/.Memória/: validar que todo arquivo tem entrada emMemória/INDEX.mde que links do índice existem.00 - INBOX/: listar itens pendentes de triagem.
Regras
- Arquivar é mover, nunca apagar.
- Não condensar handovers; eles são timeline.
- Não criar memória a partir de estado momentâneo.
- Antes de mover muitos arquivos, mostre plano curto e execute.
Checklist
- Criar pastas de arquivo se faltarem:
mkdir -p "07 - HANDOVERS/Arquivo" "07 - HANDOVERS/Tarefas/Arquivo" - Listar handovers candidatos:
find "07 - HANDOVERS" -maxdepth 1 -name "*.md" | sort find "07 - HANDOVERS/Tarefas" -maxdepth 1 -name "*.md" | sort - Ler frontmatter antes de mover.
- Validar
Memória/INDEX.mdcontraMemória/*.md. - Listar
00 - INBOX/e sugerir destino para cada item.
Relatório
Informe:
- arquivos arquivados;
- inconsistências de memória corrigidas;
- itens de inbox pendentes;
- qualquer coisa que exigiu decisão do usuário.
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.
- 6d ago First seen · 48 lines · 0 tokens per session scan A 24f346cd6e40
vault_gc is a command published in the GitHub repository PedroHenrique0713/brain-template (1 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 409 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-31.
Other commands, from other repositories
wiki-query
Ask questions against the wiki. Synthesizes answers from wiki pages with cross-reference citations.
wiki-req
Capture and decompose a concept into atomic, traceable wiki requirements. Clarifies ambiguous requirements, splits them into atomic pieces, and persists them as wiki/requirements/ pages with status tracking.
wiki-ingest
Process new source packets and synthesize them into wiki knowledge pages.
wiki-record
Capture the just-completed task's tool-call trajectory into the wiki as agent working-memory, then optionally distill it into a reusable skill.
wiki-retro
Save an atomic insight from the current task into the wiki. Creates a single markdown file that layered recall surfaces in future sessions.
wiki-discover
Auto-discover new sources from the web. Searches based on config topics and known knowledge gaps.