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/happier-dev/happier/handoff-reportnpx skills add happier-dev/happier --skill handoff-reportgit clone --depth 1 https://github.com/happier-dev/happierWrote 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/happier-dev/happier/handoff-report)<a href="https://agentmods.dev/skills/happier-dev/happier/handoff-report"><img src="https://agentmods.dev/badge/skills/happier-dev/happier/handoff-report.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.00070 | $0.00793 |
| Opus 5 | $0.00035 | $0.00396 |
| Sonnet 5 | $0.00014 | $0.00159 |
| Haiku 4.5 | $0.00007 | $0.00079 |
Grade A, and why
handoff-report 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 4d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff Report
Structure any substantive report so the reader can act on the first paragraph and audit the rest. Full doctrine: docs/agent-craft.md §5 and §7.
Order
- Outcome first. The first sentence answers what the reader would ask for if they said "just the TLDR": what happened, what was found, or what is blocked. Not the journey, not the setup.
- Failures and scope changes in the first block. A failed check, a skipped step, a scope change, an error worked around — these go up front even when embarrassing, never mid-report. The most informative event is the one you are tempted to smooth over.
- Reasoning, auditable. Evidence pointers with every load-bearing statement:
file.ts:line, the log excerpt, the measurement, the command that produced the number. Trust should rest on checkable references, not on tone. - Residual risk last, explicitly. What remains unverified, what to check next, what would invalidate the conclusion. If there is genuinely no residual risk, say that — the reader cannot distinguish "no risk" from "risk section omitted".
Labeling
- Every load-bearing statement is sortable by the reader into observed (ran it, read it, saw it) / derived (follows from observations by stated reasoning) / assumed (plausible, unverified) — without asking you.
- Use cheap explicit markers: "verified:", "inferred from X:", "assumption:". Never let sentence confidence do the labeling; fluent prose reads as fact regardless of bin.
- For derived claims, state the derivation ("X because A + B") so the reader can audit the step and see which assumptions it inherits.
- Hedging is not labeling. "Probably" makes every sentence equally gray; a label says exactly what is known and what is guessed.
- Distinguish "I didn't find X" (an observation about your search — say which search) from "X doesn't exist".
Style
- Brevity comes from selecting what matters, not compressing the writing. Complete sentences, terms spelled out, no codenames or shorthand invented mid-task.
- Write for the teammate who stepped away and is catching up — they did not watch the process unfold.
- Report faithfully: if tests failed, say so with the output; if a step was skipped, say that; if something is done and verified, state it plainly without hedging.
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.
- 4d ago First seen · 49 lines · 70 tokens per session scan A 1be1026361a9
handoff-report is a skill published in the GitHub repository happier-dev/happier (1,615 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 793 once invoked, about $0.0003 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
maple-preview
Use when a MapleStory asset request resolves to more than one plausible candidate: a look described by colour, style, or mood instead of an exact name or ID (a black cap, a white tee, a monster that suits this map), a maple-lookup search returning several close matches, or the user asking to preview, compare, or…
balance-tuning
Reviews and tunes game balance across difficulty and progression curves, session pacing, option or strategy trade-offs, and reward economies. Use when players report that a game is too hard, easy, short, long, or grindy; a weapon, upgrade, or strategy dominates; damage, health, spawn, drop, price, or progression…
cross-device-check
Audits a game's UI and interaction across supported viewports, aspect ratios, pixel densities, orientations, and input capabilities. Use when mobile, tablet, desktop, controller, keyboard, pointer, or touch support is being checked; UI clips, overlaps, blurs, or overflows; controls are unreachable or hard to use…
determinism-audit
Audits nondeterministic game behavior and flaky execution. Use when the same initial state and inputs produce different outcomes, a test fails intermittently or only under load, behavior differs by frame rate or machine, a replay diverges, or lockstep peers desynchronize. Establishes the required determinism boundary…
game-feel
Use when a game's controls feel stiff, floaty, heavy, slippery, unresponsive, or unfair; when players miss jumps they thought they made, snag on platform corners, lose inputs pressed during another action, or get hit by grazes; when a platformer, runner, or action game is being built or polished and its input and…
game-tutorial
Audits, adds, or reworks a game's first-time-player tutorial. Use when players cannot identify the controls, goal, failure conditions, or a non-obvious rule; new players quit before completing the core loop; onboarding presents too much at once; or an explicit tutorial or first-run improvement is requested. Separates…