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 agentmods add skills/sifxprime/kodelyth-ecc/agent-handoffnpx skills add sifxprime/kodelyth-ecc --skill agent-handoffgit clone --depth 1 https://github.com/sifxprime/kodelyth-eccWrote 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/sifxprime/kodelyth-ecc/agent-handoff)<a href="https://agentmods.dev/skills/sifxprime/kodelyth-ecc/agent-handoff"><img src="https://agentmods.dev/badge/skills/sifxprime/kodelyth-ecc/agent-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 | $0.00061 | $0.01415 |
| Opus 5 | $0.00030 | $0.00707 |
| Sonnet 5 | $0.00012 | $0.00283 |
| Haiku 4.5 | $0.00006 | $0.00142 |
Grade A, and why
agent-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 yesterday.
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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Handoff Protocol
Single agents handle single concerns. Real engineering tasks span multiple concerns. Handoffs are how ECC chains agents without losing context.
The 3-Line Handoff Protocol
When an agent finishes its scope and the next step needs a different specialist, it ends with exactly this shape:
─────────────────────────────────────
HANDOFF
From: <current-agent>
To: <next-agent>
Why: <one-line reason>
Carry: <what the next agent needs to know>
─────────────────────────────────────
Then stop. The next agent picks up from Carry:.
Standard Chains
These are the most common multi-agent flows. Memorize them.
Build something new (clean path)
pair-programmer → tdd-guide → code-reviewer → api-guardian (if API)
→ security-reviewer (if sensitive)
→ ux-reviewer (if UI)
pair-programmer agrees on approach. tdd-guide writes failing tests first. The implementer writes code. code-reviewer checks it. Specialist reviewers check their domain.
Bug in production
debug-detective → tdd-guide → refactor-cleaner (optional)
(root cause) (regression test)
Always add a regression test after a real-bug fix. Always.
Refactor a module
code-explorer → refactor-cleaner → tdd-guide → code-reviewer
(map dependencies) (cleanup) (verify behavior)
Performance investigation
performance-optimizer → tdd-guide → code-reviewer
(perf regression test)
API change
api-guardian → pair-programmer → tdd-guide → doc-updater
(blast radius) (impl approach) (changelog)
Security audit
security-reviewer → tdd-guide → release-captain
(security regression test) (patch release)
Open-source a private project
opensource-forker → opensource-sanitizer → opensource-packager → release-captain
(make a clean fork) (strip secrets/PII) (README, license, examples) (cut v0.1.0)
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.
- yesterday First seen · 185 lines · 61 tokens per session scan A e48faa29684c
agent-handoff is a skill published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 3d ago), licensed MIT. It adds 61 tokens to every session and 1,415 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-09-03.
Other skills, from other repositories
foolproof-product
Use this skill on ANY code change in codevira's product surface (mcpserver/, indexer/). Triggers on Edit/Write to product code, on phrases like "fix bug", "add feature", "handle error", or any modification to commands the end-user runs. Enforces 10 product- reliability principles: no silent failures, atomic state…
open-source-quality
Use this skill before committing, pushing, or opening a PR. Triggers on phrases like "commit", "git commit", "push", "open PR", "create pull request", "finalize this change". Enforces conventional commit messages, atomic commits, code style (ruff/mypy), public-API docstrings, actionable error messages, changelog…
release-readiness
Use this skill whenever the conversation mentions releasing, shipping, publishing, promoting to PyPI, "ship it", "release X.Y.Z", "ready to release", "let's publish", or any phrase suggesting moving codevira to production. Walks the 5-gate release gauntlet (G1-G5) and refuses to proceed without evidence at every gate.…
epistemic-honesty
Use this skill whenever you're about to (1) make a definitive claim like "this works", "tests pass", "ready to ship", "fixed", "done"; or (2) propose a solution to a problem; or (3) diagnose a bug or issue. Forces explicit confidence calibration with inline evidence, surfaces what you don't know, and demands a…
development-discipline
Use this skill before ANY code-writing tool call (Edit, Write, NotebookEdit) on this project. Triggers on phrases like "implement", "fix bug", "add feature", "refactor", "create function", "modify file", or whenever the user asks for a code change. Forces a 4-step CONTEXT → PURPOSE → REASON → CODE sequence with…
practical-coding
Use for implementing, fixing, refactoring, or reviewing code with the smallest correct change; routes only unresolved debugging, architecture/choice, or risk-boundary blockers, while code retrieval uses the cheapest sufficient available capability.