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/joris887/exosuit/handoffnpx skills add joris887/exosuit --skill handoffgit clone --depth 1 https://github.com/joris887/exosuitWrote 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/joris887/exosuit/handoff)<a href="https://agentmods.dev/skills/joris887/exosuit/handoff"><img src="https://agentmods.dev/badge/skills/joris887/exosuit/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.00028 | $0.01403 |
| Opus 5 | $0.00014 | $0.00701 |
| Sonnet 5 | $0.00006 | $0.00281 |
| Haiku 4.5 | $0.00003 | $0.00140 |
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 6d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
handoff
Skill metrics: Emit a start event to the activity log:
echo "{\"type\":\"skill\",\"event\":\"start\",\"skill\":\"handoff\",\"ts\":\"$(date -u +%Y-%m-%dT%H:%M:%SZ)\"}" >> docs/sessions/.activity-log.jsonl
Generate a comprehensive handoff for ending a development session:
Phase 0: Validate Prerequisites
Before starting, verify:
docs/sessions/directory exists (create if missing)- No conflicting session file for today's date
If the directory is missing, create it silently and proceed.
1. Capture Current State
Analyze:
- Current branch:
git branch --show-current - Git status (uncommitted changes?)
- Open PRs:
gh pr list --author @me --state open - Current sprint spec (if exists:
docs/sprints/sprint-*.md) — extract sprint goal, capacity used, and any decisions logged this session - Last entries in @docs/progress.md
2. Document Progress
If work was done this session, ensure it's captured:
- Sprint spec updated with progress
- Any decisions documented
- Blockers noted
3. Generate Session File
Save a structured session file to docs/sessions/session-YYYY-MM-DD.md.
The file MUST start with YAML frontmatter for /resume searchability:
---
date: YYYY-MM-DD
sprint: [current sprint number]
sprint_goal: "[sprint goal — one sentence from sprint spec]"
sprint_capacity: "[sessions used/total — e.g., 5/8]"
branch: [branch-name]
stories: [comma-separated story IDs worked on]
status: [completed | in-progress | blocked]
---
# Session Handoff — [YYYY-MM-DD]
## Git State
- **Branch:** [branch-name]
- **Uncommitted changes:** [yes/no — list if yes]
- **PR Status:** [Open #123 / Merged / Not created]
## Work Completed
- [x] [Task/story completed]
- [ ] [Task in progress — what's done, what remains]
## Key Decisions
- [Decision]: [Rationale]
## Blockers / Issues
- [Issue]: [Status]
## Files Accessed This Session
### Modified
- [path/to/file]: [what changed and why]
### Read (context-relevant)
- [path/to/file]: [why this file was important to understand]
### Investigated (can skip on resume)
- [path/to/file]: [explored but not relevant to current work]
## Test Status
- Passing: [count]
- Failing: [count]
- Coverage: [percentage if available]
## Next Steps (Minimal First Action)
1. [The single next thing to do — be very specific]
2. [Second priority]
3. [Third priority]
## Files to Load on Resume
- @[path] — [why this file is needed]
## Activity Summary
<!-- Populated from activity log if available -->
## Warnings / Gotchas
- [Any issues the next session should be aware of]
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.
- 6d ago First seen · 192 lines · 28 tokens per session scan A c6c031db703e
handoff is a skill published in the GitHub repository joris887/exosuit (4 stars, last pushed 16d ago), licensed MIT. It adds 28 tokens to every session and 1,403 once invoked, about $0.0001 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
moai-workflow-spec
SPEC workflow orchestration with EARS format requirements, acceptance criteria, and Plan-Run-Sync integration for MoAI-ADK development. Use when creating SPEC documents or defining acceptance criteria.
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
moai-workflow-templates
Template management system for code boilerplates, feedback templates, scaffolding, and project optimization workflows. Use when creating templates, generating boilerplate files, or managing scaffolding.
moai-workflow-project
Integrated project management system covering documentation, language initialization, template optimization, docs generation, and JIT document loading. Absorbed from moai-workflow-templates, moai-docs-generation, and moai-workflow-jit-docs.
moai
MoAI unified orchestrator for autonomous development. Routes natural language or subcommands (plan, run, sync, project, fix, loop, mx, feedback, review, clean, codemaps, gate, e2e, harness, goal, todo) to specialized agents.