handover_chat

handover_chat is a command for Claude Code from PedroHenrique0713/brain-template. It costs 32 tokens per session (1,271 once invoked), scanned A, original, MIT.

A command for writing a handover document that records the current session’s goal, progress, decisions, problems, and next steps. The documents are saved in a specified handover folder or active task file.

In plain words
What is it for?
Creating or updating session handovers, recording completed work and blockers, documenting technical decisions, and preparing precise follow-up instructions.
Why use it?
It preserves working context when a session ends or another AI takes over, so important details do not depend on the chat history.

Command for Claude Code

Written for Claude Code: SessionStart hook event. Also seen: mentions Codex; mentions OpenCode.

Good fit Creating or updating session handovers, recording completed work and blockers, documenting technical decisions, and preparing precise follow-up instructions.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/pedrohenrique0713/brain-template/handover_chat
Install

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.

Clone the repo
git clone --depth 1 https://github.com/PedroHenrique0713/brain-template

Made for: Claude Code.

Wrote 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.

agentmods badge for handover_chat

README.md
[![agentmods](https://agentmods.dev/badge/commands/pedrohenrique0713/brain-template/handover_chat/github.svg)](https://agentmods.dev/commands/pedrohenrique0713/brain-template/handover_chat)
Your own site
<a href="https://agentmods.dev/commands/pedrohenrique0713/brain-template/handover_chat"><img src="https://agentmods.dev/badge/commands/pedrohenrique0713/brain-template/handover_chat/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.

agentmods 80×15 button for handover_chat

Your own site · 80×15
<a href="https://agentmods.dev/commands/pedrohenrique0713/brain-template/handover_chat"><img src="https://agentmods.dev/badge/commands/pedrohenrique0713/brain-template/handover_chat.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,271 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.01271
Opus 5.5 $0.00013 $0.00508
Sonnet 5.5 $0.00006 $0.00254
Haiku 4.5 $0.00003 $0.00127

Measured 28d ago against content hash f3a06975066b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

handover_chat 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 28d 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.

vault/.claude/commands/handover_chat.md · 95 lines

How it starts

The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Salve um snapshot completo do que foi feito nesta sessão.

Definições:

  • TODAY = data de hoje em YYYY-MM-DD
  • HHMM / HH:MM = hora atual 24h (1430 / 14:30)
  • Uma tarefa são dois arquivos lado a lado em 07 - HANDOVERS/Tarefas/: o estado T0XX - nome.md (curto, reescrito a cada handover) e o log T0XX - nome.log.md (só acréscimo).

Voz e tom

Escreva como se o usuário tivesse escrito, não uma IA: 1ª pessoa do passado ("fiz", "testei", "descobri"), sem voz passiva, sem gerúndio substantivado ("realização de"), sem narração de IA ("Procedeu-se a"). Tom direto, como quem conta pro time o que aconteceu.


Passo 1 — Identificar o modo

Leia 07 - HANDOVERS/ATIVAS.md (a lista das tarefas vivas com o próximo passo de cada uma).

  • Modo Tarefa: a sessão começou com /handon, ou o que foi feito cabe numa tarefa viva. Sessão que tocou mais de uma tarefa escreve em cada uma. Em dúvida entre duas, pergunte.
  • Tarefa nova: o trabalho vai continuar em outra sessão e não tem tarefa. Crie com o script, nunca numerando à mão (sessões paralelas repetem número):
    python3 "03 - RESOURCES/Scripts/nova-tarefa.py" "Título curto" "Projeto"
    
    Depois siga o Modo Tarefa.
  • Modo Geral: só para sessão sem continuidade (planejamento, pergunta avulsa, exploração). Trabalho de um tema que tem tarefa não vira snapshot solto — senão o estado do tema fica espalhado e ninguém acha depois.

Modo Tarefa

  1. Tarefa no formato antigo? (sem o .log.md ao lado, ou com ## Log de sessões dentro do estado) → migre antes: o ## Log de sessões e tudo depois dele vão para o .log.md; seção datada solta vira entrada do log com a mesma data. Mover, nunca apagar.
  2. Estado (T0XX - nome.md), reescrevendo em vez de acrescentar:
    • frontmatter: atualizado: → TODAY; status: ∈ ativa | aguardando (com bloqueio:) | pausada | concluida | cancelada;
    • ## 📍 Estado agora e ## 🔜 Próximo passo → substitua inteiros;
    • ## ✅ Feito (não refazer) → uma linha por entrega; passando de ~15, condense (o detalhe está no log);
    • ## 🧭 Decisões técnicas → acrescente, datadas e com o porquê;
    • ## ⚠️ Armadilhas → acrescente as novas, tire as que deixaram de valer. Nada de seção nova datada no estado; alvo de até ~80 linhas. Próximo passo velho esquecido no meio do arquivo vira informação falsa.
  3. Log (T0XX - nome.log.md): acrescente ao final:

Read the full file on GitHub · 95 lines

Changes

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.

  1. 28d ago Changed · +31 lines · +5 tokens per session f3a06975066b
  2. 1mo ago First seen · 64 lines · 27 tokens per session scan A 43da5153077b

Subscribe to this mod's changes

handover_chat is a command published in the GitHub repository PedroHenrique0713/brain-template (1 stars, last pushed 15d ago), licensed MIT. It adds 32 tokens to every session and 1,271 once invoked, about $0.0001 per session on Opus 5.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.