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 AshExplained/roblox-skills --skill handoffgit clone --depth 1 https://github.com/AshExplained/roblox-skillsWrote 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/ashexplained/roblox-skills/handoff)<a href="https://agentmods.dev/skills/ashexplained/roblox-skills/handoff"><img src="https://agentmods.dev/badge/skills/ashexplained/roblox-skills/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/ashexplained/roblox-skills/handoff"><img src="https://agentmods.dev/badge/skills/ashexplained/roblox-skills/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.00065 | $0.00670 |
| Opus 5.5 | $0.00026 | $0.00268 |
| Sonnet 5.5 | $0.00013 | $0.00134 |
| Haiku 4.5 | $0.00006 | $0.00067 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff
Write a concise handoff document so a fresh agent can continue from the current state without rereading the whole conversation.
When to use
- User asks for
/handoff, "handoff this", "handoff to /prototype", "handoff back", "summarize for next session", or "another agent should continue". - A long planning, prototype, diagnosis, or implementation thread is about to switch focus or end.
- A side quest should run in another session and return with a compact verdict.
Process
- Identify the handoff target. If the user passed arguments, treat them as the next session's focus, such as
/prototype,/tdd, or "back to grilling session". - Create
.scratch/handoffs/if needed. - Save the handoff as
.scratch/handoffs/YYYY-MM-DD-<short-slug>.md. Use the current local date and a slug for the target or topic. If a file already exists, append a short numeric suffix rather than overwriting. - Before writing, read any existing file at that path so you do not clobber prior notes.
- Write only the context the next agent actually needs.
Content
Include:
- Goal: what the next session should do.
- Current state: what has already been decided or done.
- Key unresolved questions.
- Relevant artifacts: PRDs, issues, ADRs, design docs, prototype paths, commits, diffs, URLs.
- Suggested next skill or command.
- Return instructions: what result should come back to this thread or parent skill.
Do not duplicate content already captured in PRDs, plans, ADRs, issues, commits, diffs, or prototype notes. Reference them by path or URL.
Patterns
- "handoff to /prototype" -> explain the question the prototype must answer, the relevant app/module context, and that prototype output is disposable.
- "handoff back" -> summarize what the side quest learned, where the artifact lives, and what decision can now be made.
- "handoff to implementation" -> point at the approved PRD/issues/design artifacts and note remaining risks.
Anti-patterns
- Do not turn the handoff into a full project history.
- Do not write vague instructions like "continue the work"; name the next concrete move.
- Do not put durable project decisions only in the handoff. If a decision belongs in
CONTEXT.md, an ADR, an issue, or a PRD, put it there and link to it.
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 · 53 lines · 65 tokens per session scan A b436c00f9ffe
handoff is a skill published in the GitHub repository AshExplained/roblox-skills (29 stars, last pushed 3mo ago), licensed MIT. It adds 65 tokens to every session and 670 once invoked, about $0.0003 per session on Opus 5.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
session-handoff
Use when a working session is ending, the context window is nearly full, work needs to pass to a teammate or a fresh session, or the user says "hand this off", "write this up before we lose it", "I'm starting a new session", or "summarize where we are". Produces a handoff document that lets the next session resume…
context-budget
Use when a coding session is burning context fast, output is drowning in noise, the model keeps forgetting earlier decisions, or the user asks to reduce tokens, stop the verbose narration, work in a huge repo, or make a long session survive. Covers what to read, what to summarize, what to write to disk, and when to…
conversation-archaeologist
Mine ALL past Claude conversations to build a living 'User Manual About You'. Extract writing style, business context, goals, preferences, and patterns. Make all other skills smarter with context.
magic-compact
Compact this Claude Code session.
skill-status
A study-progress companion that reads a saved JSON file to remember your learning plan, progress, predictions, and past notes between sessions.
distill-habits
Review recent coding-agent conversations (Claude Code or Codex), distill the user's stable habits and preferences, persist them into a long-term habit ledger, and maintain a "My Habits" block in the agent's global instructions file (CLAUDE.md or AGENTS.md) within a character budget. The more you use the agent, the…