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/gleanwork/claude-plugins/project-handoffnpx skills add gleanwork/claude-plugins --skill project-handoffgit clone --depth 1 https://github.com/gleanwork/claude-pluginsWhat 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.00105 | $0.01953 |
| Opus 5 | $0.00053 | $0.00977 |
| Sonnet 5 | $0.00021 | $0.00391 |
| Haiku 4.5 | $0.00011 | $0.00195 |
Grade A, and why
project-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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- project-handoff — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Handoff
Generate a comprehensive handoff document so someone new can take over a project. Gather everything they'd need: current state, the people who matter, tribal knowledge, open items, and a concrete ramp-up plan.
Determine the project from the user's request. If no project is clear, ask which project they mean before proceeding.
This is the heavyweight counterpart to the project-awareness skill (quick status reads). Use that one if the user just wants current status.
Tools
This skill drives the standard Glean MCP tools. If the host exposes the
project-synthesizer agent, use it for project research. Otherwise delegate to
a suitable research subagent when subagents are available, or gather the same
material directly. For the param shape and pitfalls of search, chat,
meeting_lookup, and employee_search, see the using-glean reference at
using-glean/reference/. If no Glean tools are visible, ask the user to set up
Glean by prompting the harness (for example, Set up Glean for me).
Core Principles
- Complete context: include everything needed to take over
- Actionable items: clear next steps and open items
- Tribal knowledge: capture what's not in docs
- Be skeptical: not every doc found is relevant to a handoff
- Quality over quantity: focus on what the new owner actually needs
Phase 1: Gather current context
Understand the project's current state.
- Ask the user for handoff context:
- Their role on the project (Owner/Lead, Contributor, Advisor/Stakeholder)
- What's driving the handoff (new role/team, PTO coverage, reorg, leaving)
- Use
project-synthesizerwhen available; otherwise delegate to a suitable research subagent if possible, or gather the material directly. Cover documentation, people and their roles, recent meetings and decisions, and current status / open items.
Phase 2: Gather undocumented knowledge
Capture tribal knowledge not in formal docs. Ask the current owner:
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.
- 3d ago First seen · 204 lines · 105 tokens per session scan A 99224b4a3ac3
project-handoff is a skill published in the GitHub repository gleanwork/claude-plugins (25 stars, last pushed 13d ago), licensed MIT. It adds 105 tokens to every session and 1,953 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…