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 gleanwork/cursor-plugins --skill project-handoffgit clone --depth 1 https://github.com/gleanwork/cursor-pluginsWrote 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/gleanwork/cursor-plugins/project-handoff)<a href="https://agentmods.dev/skills/gleanwork/cursor-plugins/project-handoff"><img src="https://agentmods.dev/badge/skills/gleanwork/cursor-plugins/project-handoff/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/gleanwork/cursor-plugins/project-handoff"><img src="https://agentmods.dev/badge/skills/gleanwork/cursor-plugins/project-handoff.svg" alt="Reviewed on agentmods" width="80" 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.00105 | $0.01953 |
| Opus 5.5 | $0.00042 | $0.00781 |
| Sonnet 5.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 1mo 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.
This is a copy
100% identical to project-handoff — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 1mo ago First seen · 204 lines · 105 tokens per session scan A 99224b4a3ac3
project-handoff is a skill published in the GitHub repository gleanwork/cursor-plugins (4 stars, last pushed 17d ago), licensed MIT. It adds 105 tokens to every session and 1,953 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to project-handoff, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
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.
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…