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 skills add flurdy/agent-skills --skill handoffs-tidygit clone --depth 1 https://github.com/flurdy/agent-skillsWrote 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/flurdy/agent-skills/handoffs-tidy)<a href="https://agentmods.dev/skills/flurdy/agent-skills/handoffs-tidy"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/handoffs-tidy/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.
<a href="https://agentmods.dev/skills/flurdy/agent-skills/handoffs-tidy"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/handoffs-tidy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 6 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00051 | $0.02971 |
| Opus 5 | $0.00026 | $0.01486 |
| Sonnet 5 | $0.00010 | $0.00594 |
| Haiku 4.5 | $0.00005 | $0.00297 |
Grade A, and why
handoffs-tidy 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 9d 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoffs-tidy — retire handoffs that no longer point at live work
Keep ~/.claude/handoffs/ focused on live threads. Handoffs go stale three ways, and the
common one isn't supersede:
- Superseded — a newer handoff continues the same thread (same branch / topic / same-day re-wrap).
- Done — the work shipped: its PR merged, every referenced bead is closed, the branch landed, or
its Jira ticket is Done. These are usually never re-wrapped, so nothing supersedes them — they
just sit in the picker looking
🟢 liveuntil you notice the work is long gone. - Stale — abandoned: the PR was closed unmerged, or the branch is gone with no merge evidence.
- Old and signal-less — unknown branch liveness with no usable PR signal or resolvable beads. Age only earns an assisted question; it never makes the handoff an automatic archive candidate.
This command finds all four and archives the ones you confirm. A recent handoff is retained even when
finished or stale; superseded rows are the sole immediate exception. Nothing is deleted — archived
files move to ~/.claude/handoffs/archive/ and stay greppable.
Run it ad-hoc whenever the picker feels noisy, or right after a /wrap-up. It is the standalone
twin of /handoffs's opt-in archive step (§3b): same list.sh classification, same archive flow —
shared verbatim via REFERENCE.md — but with no full table, no picker, and no resume step. It only
ever offers candidates; it never touches a live or open-PR row.
Earlier versions only found superseded handoffs (it ran
list.shwith no flags and looked at one field). That's why it rarely found anything — supersede is the narrowest signal. From v0.2.0 it runs the full liveness pass, so finished-but-never-re-wrapped handoffs finally surface.
When to use
- After a
/wrap-upwhose handoff continued an earlier thread, or whose work has now shipped. - Periodically, when
/handoffsshows entries you've moved past — merged PRs, closed beads, dead branches. - Not needed if you keep only one live handoff per topic and archive as you go.
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.
- 9d ago First seen · 195 lines · 51 tokens per session scan A 3bc9292553d4
handoffs-tidy is a skill published in the GitHub repository flurdy/agent-skills (9 stars, last pushed 3d ago), licensed MIT. It adds 51 tokens to every session and 2,971 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.