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 DDS-Solutions/AI-TadPole-OS --skill handoffgit clone --depth 1 https://github.com/DDS-Solutions/AI-TadPole-OSWrote 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/dds-solutions/ai-tadpole-os/handoff)<a href="https://agentmods.dev/skills/dds-solutions/ai-tadpole-os/handoff"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/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/dds-solutions/ai-tadpole-os/handoff"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/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.00034 | $0.01830 |
| Opus 5.5 | $0.00014 | $0.00732 |
| Sonnet 5.5 | $0.00007 | $0.00366 |
| Haiku 4.5 | $0.00003 | $0.00183 |
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 12d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[!IMPORTANT] AI Context & Knowledge Heritage
- Subsystem: Agent Skills Registry / handoff
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: Information drift, lost session state, or uncoordinated agent transitions.
- Observability: Traceability via
execution/parity_guard.py([SKILL])
Session Handoff & State Transfer Protocol
Purpose: Compact active session state into a high-signal, zero-bloat handoff artifact so a fresh agent session or specialist subagent can resume execution immediately with zero context token degradation.
Workflow Bindings: Integrated into/orchestrate,/onboard, and/status.
📚 Progressive Disclosure & L3 Reference Index
Consult deep L3 Reference Guides and verification tools on demand:
- Handoff Schema & Protocols:
references/handoff_schema_and_protocols.md - Deterministic Handoff Manager:
scripts/handoff_manager.py - Context Compactor & Checkpoints:
context_compactor.py
🚦 1. When to Trigger a Session Handoff
Trigger a session handoff under any of the following operational conditions:
- Turn Count Ceiling: Active session reaches 15–20+ conversational turns.
- Phase Boundary Transition: Shifting from Planning/Architecture to Deep Implementation, or from Implementation to Security Audit / Testing.
- Agent Delegation (PEC): Transferring task ownership from a Coordinator Agent (e.g. Agent 2 / Tadpole Alpha) to a Worker Subagent.
- Session Suspension: Halting work across sessions or prompting the user before a long-running execution.
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.
- 12d ago Changed · +111 lines · +14 tokens per session e33a11c42a65
- 1mo ago First seen · 43 lines · 20 tokens per session scan A 03342aab1f09
handoff is a skill published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 1,830 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
anarlog
Query Anarlog meetings, notes, summaries, transcripts, participants, action items, and recurring history, or import a local recording. Use when a user asks about their Anarlog meeting data or needs meeting context for another task.
frontend-ai-guide
Applies React/TypeScript-specific technical decision criteria, anti-pattern detection, debugging, and frontend quality gates. Use when reviewing components, hooks, browser behavior, or frontend implementation completeness.
walkeros-create-transformer
Use when creating a new walkerOS transformer to modify events in the pipeline (validate, enrich, or redact) at a before/next chain position. Example-driven workflow for the transformer interface, return values, and chaining.
optimizing-clickhouse-and-hogql-queries
Workflow for optimizing ClickHouse and HogQL queries. Use when a HogQL query, query runner, insight, or report is too slow; when a hand-written ClickHouse query (via syncexecute or in a migration) is too slow; when ClickHouse times out or hits memory limits; when investigating a slow system.querylog row; or when…
dynamic-workflows
Designs and runs task-specific JavaScript harnesses with the workflow tool. Use for broad, long-running, highly structured, or adversarial work that benefits from many isolated agents: exhaustive audits, root-cause investigations, research, large triage queues, competing proposals, repeated verification, and…
adding-product-alerting
Recommended repo-engineering guide when adding alerting to a PostHog product or extending the shared alerts platform. Routes lifecycle state machines, AlertPolicy, destinations, HogFunction dispatch, email, fixed-cadence and calendar scheduling, insight evaluation, the AlertWizard, and shared alert editor components.…