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/pvrlabs/aibadger/handoffnpx skills add PVRLabs/aibadger --skill handoffgit clone --depth 1 https://github.com/PVRLabs/aibadgerWrote 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/pvrlabs/aibadger/handoff)<a href="https://agentmods.dev/skills/pvrlabs/aibadger/handoff"><img src="https://agentmods.dev/badge/skills/pvrlabs/aibadger/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 | $0.00035 | $0.00403 |
| Opus 5 | $0.00017 | $0.00201 |
| Sonnet 5 | $0.00007 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00040 |
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 yesterday.
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
Badger Handoff
Create .badger-handoff in the current working directory, or another workspace
directory explicitly selected by the user. Do not discover a Git root.
Summarize the session concisely and with high information density. Preserve enough context to continue without repeating investigation or misunderstanding a decision. Give later decisions and corrections precedence.
Remove conversational noise, repetition, obsolete details, and information Badger can recover from the repository. Preserve the current goal, material progress, decisions and rationale, constraints and non-goals, completed work, verification results, significant failed approaches, blockers, and immediate next steps. Include exact details only when they are necessary for continuity.
Aim for no more than 2,000 output tokens under normal circumstances. Use less for simple sessions. Exceed this target only when further compression would discard continuation-critical information.
Use mode: handoff when repository work is part of the session. Use
mode: design only for reasoning where current worktree state is irrelevant.
Write this exact UTF-8 framing:
BADGER-HANDOFF-V1
mode: handoff
<compact session summary>
Keep the complete file at or below 65,536 bytes. The body is conversation state only: do not inspect or include repository files, diffs, Git state, or topology. Badger collects repository context itself.
After writing successfully, derive the absolute directory from the written file path and print exactly:
Badger handoff prepared.
In a separate terminal, run:
cd '/absolute/path/to/the-written-directory'
badger continue
Substitute the actual POSIX-shell-quoted directory. Do not invoke Badger or use another transport.
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.
- yesterday Changed · +9 lines a419b6c2a678
- 5d ago First seen · 45 lines · 35 tokens per session scan A fa52bab9cdbc
handoff is a skill published in the GitHub repository PVRLabs/aibadger (30 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 403 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-30.
Other skills, from other repositories
token-guard
Use Codex Token Guard to reduce noisy command and tool-output tokens while preserving errors, file paths, line numbers, test names, user instructions, recent edits, and architecture decisions.
dcf-model
Build discounted cash flow valuation workbooks in Excel.
hermes-agent-skill-authoring
Author in-repo SKILL.md files: frontmatter and structure.
baoyu-article-illustrator
Article illustrations: type × style × palette consistency.
flash-attention
Speed up long-sequence transformer training and inference.
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).