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/tradebaas/groundwork/handovernpx skills add Tradebaas/Groundwork --skill handovergit clone --depth 1 https://github.com/Tradebaas/GroundworkWhat 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.00056 | $0.00536 |
| Opus 5 | $0.00028 | $0.00268 |
| Sonnet 5 | $0.00011 | $0.00107 |
| Haiku 4.5 | $0.00006 | $0.00054 |
Grade A, and why
handover 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 2d 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.
What it actually says
handover: the repo must speak for itself
The test is always the same: a competent stranger, any IDE, any model, gets only the repo. Can they continue within ten minutes? If anything requires this conversation, your memory, or files outside the repo, the handover is broken.
The audit
Walk it as the stranger would:
README.md→ do the copy/start instructions still hold for this project?AGENTS.mdrouting table → does every row point at a file that exists and is current?docs/state/STATE.mdhandoff block → status, phase, branch, gates, Now ▶, blockers. Is it literally true right now? Stale handoff is the most damaging lie in the system.docs/product/BRIEF.md→ does it still describe the product that exists?- Can the stranger run it? Setup steps, env vars (
.env.examplecomplete?), seed data,docs/operations/runbooks. Follow them literally; fix what's wrong, don't annotate around it. A fresh clone must also re-runnode checks/check.mjs --install-hooks. Is that step where the stranger will see it (README/setup)? - Secrets and access: nothing secret in the repo, and a named list of what access a successor
must be granted (where credentials live, who grants them) in
docs/operations/access.md. - Open threads: in-flight specs at their real status; INTAKE triaged or explicitly queued;
DEBT.md reconciled with
defer:markers.
Fix everything fixable now. What you can't fix, write down as an explicit gap in STATE.md. A named gap is transferable; a hidden one isn't.
Human handover (milestone/project end)
Add a dated entry to STATE.md's log: what was delivered, where it runs, the three things a successor must know first, and the owner's open decisions. If the successor is non-technical, point them at README; if technical, at AGENTS.md. Nothing else to produce. If a separate "handover document" feels needed, the repo is failing this skill; fix the repo instead. ⚓
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.
- 2d ago First seen · 39 lines · 56 tokens per session scan A 751007cdfb03
handover is a skill published in the GitHub repository Tradebaas/Groundwork (2 stars, last pushed 7d ago), licensed MIT. It adds 56 tokens to every session and 536 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
mission-driver
Create roadmaps and mission configs, then drive the mission-driver AI dev-loop engine. mission-driver lives at tools/mission-driver/ — it reads missions/ .json and loops CHECK → REVIEWPLANS → EXECPLANS → DRAFTPLANS → DEEPAUDIT until the roadmap is done or the audit budget is exhausted. Use this skill when the user…
keel-plan
Create or revise PLAN.md — propose the phase DAG (phases · gates · dependencies) from the user's goal, get approval, write the table and regenerate the colored Mermaid diagram from it. Statuses flip at rituals (/keel-handover, /keel-phase-review); post-completion fixes land in the Fix log.
keel-stats
Render the ritual telemetry visually — turns .claude/ritual-log into reports/ritual-stats.md with PLAN.md-style colored Mermaid interval boxes (session/compact boundaries) + a counts table. Answers "which skills/commands/hooks ran, how often, in which interval".
sdd-serve
Serve the SDD Builder's AI request queue: claim requests with sddnextrequest, draft the proposal, answer with sddrespondrequest. Never writes spec files — the user accepts each proposal in the builder. Use when the user asks to attend, serve or listen to the SDD board queue. / Atiende la cola de peticiones del SDD…
init
Configure an uninitialized project from an approved charter: stack, scripts, identity, optional Git, and verification.
sdd-workflow
Guide a project with Spec-Driven Development (SDD) discipline - idea, approved spec, consistent plan, tasks, a gate that verifies approval and consent, implementation, validation, and logbook. Bilingual EN/ES. Use when the user wants to start, spec, plan, implement, or validate work with SDD, or mentions specs, plans…