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 berkcangumusisik/agent-hub --skill handoffgit clone --depth 1 https://github.com/berkcangumusisik/agent-hubWrote 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/berkcangumusisik/agent-hub/handoff)<a href="https://agentmods.dev/skills/berkcangumusisik/agent-hub/handoff"><img src="https://agentmods.dev/badge/skills/berkcangumusisik/agent-hub/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/berkcangumusisik/agent-hub/handoff"><img src="https://agentmods.dev/badge/skills/berkcangumusisik/agent-hub/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.00052 | $0.00277 |
| Opus 5 | $0.00026 | $0.00138 |
| Sonnet 5 | $0.00010 | $0.00055 |
| Haiku 4.5 | $0.00005 | $0.00028 |
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 10d 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
Capture the state of the current work so it can be resumed cold.
Steps
- If a profile exists, read
.claude/agent-hub/profile.ymlfor project context. - Produce a short, skimmable handoff with these sections:
- Goal — what we're trying to achieve (one or two lines).
- Done — what changed this session (files, decisions), with paths.
- Current state — what works, what's verified, what's still broken.
- Next steps — the concrete, ordered actions to take next.
- Open questions / risks — anything blocking or undecided.
- How to run/test — the exact commands from the profile.
- Keep it tight — bullets, file paths, no filler. Optimize for someone with zero context.
- Offer to save it to
.claude/agent-hub/handoff.md(overwrite the previous one) so it persists for the next session. Only write the file if the user confirms.
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.
- 10d ago First seen · 22 lines · 52 tokens per session scan A 8a35437e83dc
handoff is a skill published in the GitHub repository berkcangumusisik/agent-hub (14 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 277 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-30.
Other skills, from other repositories
composio
Route and complete Composio work across Composio For You and Composio Platform. Use when the user mentions Composio; wants an agent to use apps such as Gmail, Slack, GitHub, Notion, Calendar, or Linear; needs first-time setup, an SDK or MCP integration, CLI operation, migration guidance, current documentation, or help…
omnigent-knowledge
Deep reference on Omnigent config format, executor types, skill/tool structure, and conventions. Load when you need to look up how the platform works.
build-omnigent
Patterns and templates for generating valid Omnigent agent directories. Load when ready to create files.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
detect-framework
Detect Python agent frameworks from code imports and map them to Omnigent executor types. Load when the user has existing agent code to integrate.
api-docs
Document a module or public API surface (functions, classes, CLI commands, endpoints) from the code itself. Use when the user asks for API reference, to document a module, or to write usage docs for a public interface.