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 zarpay/rails-template --skill handoffgit clone --depth 1 https://github.com/zarpay/rails-templateWrote 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/zarpay/rails-template/handoff)<a href="https://agentmods.dev/skills/zarpay/rails-template/handoff"><img src="https://agentmods.dev/badge/skills/zarpay/rails-template/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.00045 | $0.01637 |
| Opus 5 | $0.00023 | $0.00818 |
| Sonnet 5 | $0.00009 | $0.00327 |
| Haiku 4.5 | $0.00005 | $0.00164 |
Grade A, and why
superpowers-ruby: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 7d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff
Overview
Capture the current session's state into a structured handoff document so a future session (or a different agent) can resume without losing context. The handoff document records goals, decisions, progress, and next steps.
Core principle: Capture what the next session needs to know — not everything that happened.
Announce at start: "I'm using the handoff skill to capture session state."
When to Use
- Before ending a long session with unfinished work
- Before switching to a different task or branch
- When context is getting large and compaction is likely
- When handing off work to another person or agent
Don't use when:
- Work is fully complete (use
superpowers-ruby:finishing-a-development-branchinstead) - Capturing a solved problem (use
superpowers-ruby:compoundinstead)
Quick Reference
/superpowers-ruby:handoff # Create a full handoff document
/superpowers-ruby:handoff-resume # Resume from the latest handoff
/superpowers-ruby:handoff-list # List available handoffs
Output location: docs/handoffs/YYYY-MM-DD-<topic>.md
Archive location: docs/handoffs/_archive/
The Process
Step 1: Gather Mechanical State
Run these commands to collect file-level state:
# Modified files
git diff --name-only
git status --porcelain
# Detect plan files
ls .claude/plans/*.md 2>/dev/null
ls docs/superpowers/specs/*.md 2>/dev/null
ls docs/superpowers/plans/*.md 2>/dev/null
Step 2: Generate Topic
Derive a short topic slug from the current work context. Use the branch name as a starting point, stripped of prefixes like feature/, fix/, lg/. If no branch context, ask the user or derive from the goal.
Topic slug guidelines:
- Describe the work being done, not the branch or ticket —
auth-jwt-migrationnotfix-authorJIRA-1234 - Use 2-4 words in lowercase kebab-case, max 40 characters — enough to distinguish at a glance when scanning
docs/handoffs/ - Focus on the subject and action — what thing is being changed and how:
stimulus-form-validation,stripe-webhook-retry-logic - Avoid generic slugs like
bugfix,refactor,updates— these are meaningless when you have 10 handoffs in the directory - When in doubt, match the style of existing handoffs in
docs/handoffs/— consistency beats cleverness
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.
- 7d ago First seen · 160 lines · 45 tokens per session scan A a0955e377a56
superpowers-ruby:handoff is a skill published in the GitHub repository zarpay/rails-template (9 stars, last pushed 25d ago), licensed MIT. It adds 45 tokens to every session and 1,637 once invoked, about $0.0002 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.