Borrowing it
Nothing to install: this file belongs to glslang/windbg-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/glslang/windbg-mcp/main/.claude/skills/handoff/SKILL.mdgit clone --depth 1 https://github.com/glslang/windbg-mcpWrote 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/glslang/windbg-mcp/handoff)<a href="https://agentmods.dev/skills/glslang/windbg-mcp/handoff"><img src="https://agentmods.dev/badge/skills/glslang/windbg-mcp/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.00096 | $0.04305 |
| Opus 5 | $0.00048 | $0.02152 |
| Sonnet 5 | $0.00019 | $0.00861 |
| Haiku 4.5 | $0.00010 | $0.00430 |
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.
How it starts
The opening of the file, as written. The whole thing — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handing the work over
The files a handoff touches
"Update the handoff docs" means a specific set, discoverable only from what the handoff PRs touched
(#155, #159, #170). They are titled "Hand the <X> work over: …" — the stem is the convention,
and the clause after the colon says what kind of handoff it is: "the traps, not just the result"
on #159 and #170, "what is covered, what is not" on #155.
-
CLAUDE.md— the two roles, the release-exe lock, and the routing table naming every rule and skill below. It is loaded into every session, so what goes here is what every session needs; anything longer belongs in one of the next two. -
.claude/rules/*.md— what bites while editing a subsystem, scoped by apaths:glob so it loads only when Claude reads a file it covers. A new subsystem note goes in the rule whose subject it belongs to; the scope is not part of that choice, for the reason below.paths:is one shared scope for the nine code rules, and that is a decision rather than laziness. Each was first scoped to the files named in its own title, which is the natural thing to do and was wrong fifteen times: nine filed as review findings across rounds one to nine of #285, six more found by enumerating rather than waiting for the next round — and the ninth landed after the shared scope, againstcargo-and-dependencies, whose first paragraph bound a Rust-only change from a manifest-scoped file.worker-architecturebindsworker.rsandproto.rs,listener-clientsbindsserver.rsandengine.rs,tool-surfacebindsworker.rs,execution-waitsbindsserver.rs,batch.rsandstructured.rs,transcriptsbindsmain.rs,server.rsandengine.rs, and so on. Two heuristics were tried and both failed: "start from the four hub files" cannot reachbatch.rs, which is bound by what it routes; and a lint over symbols a rule names returns mostly collisions, because tool names and English words are the same strings as this crate's items (cargo-and-dependencies"names"engine.rsthrough registry,transcriptsnamesserver.rsthrough theregisterstool, andArchandExpiredare each defined in two modules meaning different things).
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 First seen · 220 lines · 96 tokens per session scan A b64f4194318d
handoff is a skill published in the GitHub repository glslang/windbg-mcp (9 stars, last pushed 2d ago), licensed MIT. It adds 96 tokens to every session and 4,305 once invoked, about $0.0005 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-09-06.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.