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 korbinjoe/TeemAI --skill handoffgit clone --depth 1 https://github.com/korbinjoe/TeemAIWrote 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/korbinjoe/teemai/handoff)<a href="https://agentmods.dev/skills/korbinjoe/teemai/handoff"><img src="https://agentmods.dev/badge/skills/korbinjoe/teemai/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.00026 | $0.00413 |
| Opus 5 | $0.00013 | $0.00206 |
| Sonnet 5 | $0.00005 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00041 |
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.
What it actually says
Handoff
Transfer your current task to a more appropriate Agent. After a successful handoff, exit cleanly — the target Agent takes over.
How to Handoff
- Summarize what you've done so far and what you've discovered
- Identify the most appropriate target Agent
- Call:
bash {SKILL_DIR}/scripts/handoff.sh <agentId> "<task>" '<context-json>' - If the script exits 0 (HANDOFF_OK), exit cleanly — your work is done
- If the script exits 1 (HANDOFF_FAILED), continue working on the task yourself
Context JSON Format
{
"originalUserMessage": "what the user originally asked",
"workDoneSoFar": "summary of what you accomplished",
"relevantFiles": ["file1.ts", "file2.tsx"],
"keyFindings": ["insight 1", "insight 2"]
}
Handoff Targets
| Task domain | Target Agent |
|---|---|
| Visual/UI/styling/design | ui-designer |
| Code review/quality audit | code-reviewer |
| Architecture/module boundaries/refactoring | architect |
| Deploy/CI/CD/infrastructure | devops-engineer |
| Implementation/bug fixes/features | fullstack-engineer |
| Logo/icon/image creation | image-creator |
| Product research/PRD/competitive analysis | product-strategist |
| Promotion/X posts/social media | growth-marketer |
| Agent evolution/prompt optimization | sensei |
Constraints
- Max 1 handoff per task (no chained handoffs)
- Same chat only
- No self-handoff
Calling Convention
Use Bash's description parameter: Handoff to <agentId>
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 56 lines · 26 tokens per session scan A 0e7279086190
handoff is a skill published in the GitHub repository korbinjoe/TeemAI (2 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 413 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
starting-a-new-project
Use when the workspace is empty — no code yet — and the user brings a raw idea: the brand-new branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for features in an existing project — use brainstorming instead.
agent-spec-estimate
An effort-estimation method for agent-spec Task Contracts, which are structured descriptions of software work. It estimates work in rounds, meaning cycles of an AI agent doing and checking tasks.
agent-spec-intent-compiler
Use when converting PRD or issue prose into KLL requirements, running the intent compiler plan, or reverse-interviewing a human to resolve requirement ambiguity before task spec generation.
agent-spec-wiki
Use when initializing, checking, enriching, or reviewing agent-spec code live wiki pages, sourcefiles trace, or Rust architecture inventory.
todos
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.