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/fatihkan/badiWrote 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/fatihkan/badi/handoff)<a href="https://agentmods.dev/commands/fatihkan/badi/handoff"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/handoff.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.00000 | $0.00590 |
| Opus 5 | $0.00000 | $0.00295 |
| Sonnet 5 | $0.00000 | $0.00118 |
| Haiku 4.5 | $0.00000 | $0.00059 |
Grade A, and why
handoff 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 today.
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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff briefing command. Enables a smooth transition to another developer or session.
Required Tools
- Read (context, notes, tasks)
- Bash (git status)
- Write (handoff file)
Procedure (5 Steps)
Step 1: Gather Context
Build the full picture of the current state:
- Read
memory.md - Review the daily notes
- Check the git status (branch, uncommitted changes)
- Read the task board
- Check previous handoff notes
Step 2: Document Achievements
List the work completed in this period:
- Completed features and improvements
- Fixed bugs
- Completed research or analyses
- Architectural decisions taken and their rationale
- Refactoring or cleanup work done
Step 3: Identify Prerequisites
Prepare what the recipient needs:
- Development environment requirements
- Special configuration or access needs
- Migrations or scripts that must be run
- Environment variables
- Third-party service access details (excluding secrets)
Step 4: Build the Recipient Context
So the person taking over can start immediately:
- Current branch state and where it merges
- Open tasks in priority order
- Known issues and workarounds
- Blocked work and what it waits on
- Test status (passing/failing tests)
- Critical deadlines
Step 5: Create the Handoff File
Create handoffs/handoff-[DDMMYY].md:
# Handoff Briefing - [date]
## Project Summary
[the project's current state, 2-3 sentences]
## Period Summary
**Start:** [date]
**End:** [date]
**Focus Area:** [main work area]
## Achievements
- [list of completed work]
## Current State
### Branch Status
- Active Branch: [branch name]
- Base: [target branch]
- Uncommitted Changes: [yes/no]
- CI Status: [passed/failed/pending]
### Open Tasks (In Priority Order)
1. **[HIGH]** [task description]
- Status: [status]
- Next step: [step]
2. **[MEDIUM]** [task description]
...
### Known Issues
- [issue]: [workaround or plan]
### Blocked Work
- [work]: [why blocked, waiting on whom/what]
## Prerequisites
- [environment requirements]
- [configuration steps]
## Critical Dates
- [date]: [for what]
## Important Files
- [file path]: [why it matters]
## Notes and Warnings
[special situations to watch]
## Contact
[contact info for questions]
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.
- today First seen · 102 lines · 0 tokens per session scan A 5ae23e7e0c71
handoff is a command published in the GitHub repository fatihkan/badi (7 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 590 tokens. 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-09-06.
Other commands, from other repositories
plan-start
5-phase planning command: PRD analysis, design review, technical decisions, dynamic research team, metrics. Produces a complete implementation plan + ADRs before any code is written.
plan-ceo-review
Strategic product gate — challenge the brief, find the 10-star product hiding inside the request, before writing any code.
routines-discover
Analyzes the current project to surface high-value Routines use cases across the three trigger types (schedule, API, GitHub events). Usage: /routines-discover.
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524) — sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
methodology-advisor
Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack.
review-pr
Perform a comprehensive code review of a pull request.