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 bug-ops/zeph --skill rust-agent-handoffgit clone --depth 1 https://github.com/bug-ops/zephWrote 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/bug-ops/zeph/rust-agent-handoff)<a href="https://agentmods.dev/skills/bug-ops/zeph/rust-agent-handoff"><img src="https://agentmods.dev/badge/skills/bug-ops/zeph/rust-agent-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/bug-ops/zeph/rust-agent-handoff"><img src="https://agentmods.dev/badge/skills/bug-ops/zeph/rust-agent-handoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00085 | $0.03073 |
| Opus 5.5 | $0.00034 | $0.01229 |
| Sonnet 5.5 | $0.00017 | $0.00615 |
| Haiku 4.5 | $0.00009 | $0.00307 |
Grade A, and why
rust-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 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 — 367 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rust Agent Handoff Protocol
Subagents work in isolated context — they cannot see each other's conversations. This protocol enables structured communication through flat YAML files.
Directory Structure
.local/
└── handoff/
├── 2025-01-09T14-30-45-architect.yaml
├── 2025-01-09T15-00-00-developer.yaml
└── ...
File Naming Convention
[!IMPORTANT] Filename MUST equal
{id}.yaml- The handoff file name must exactly match theidfield inside the YAML file.
Format: {id}.yaml where id = {timestamp}-{agent}
Example:
- Handoff id:
2025-01-09T14-30-45-architect - Filename:
2025-01-09T14-30-45-architect.yaml
| Agent | Agent suffix in id |
|---|---|
| rust-architect | architect |
| rust-developer | developer |
| rust-testing-engineer | testing |
| rust-performance-engineer | performance |
| rust-security-maintenance | security |
| rust-code-reviewer | review |
| rust-cicd-devops | cicd |
| rust-debugger | debug |
| rust-critic | critic |
Communication Model
Parent Agent (or User)
│
├── Task(rust-architect): "Design system"
│ ↓
│ rust-architect executes
│ - reads handoff if path provided
│ - does work
│ - writes handoff file
│ - RETURNS result with handoff path
│ ↓
├── receives result, reads handoff path
│
├── Task(rust-developer): "Implement. Handoff: <path>"
│ ↓
│ rust-developer executes
│ ...
Key point: Subagents cannot call each other directly. They return results to parent, who orchestrates the next call.
On Startup
If handoff file path(s) provided in task description:
Single handoff:
cat <provided-path>
Multiple handoffs (when merging contexts):
cat <path1>
cat <path2>
# ...
Reading parent context (recommended):
After reading the provided handoff, read its parent reports to understand the full context chain:
What ships with it
9 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.
- 1mo ago First seen · 367 lines · 85 tokens per session scan A 68af9381fc43
rust-agent-handoff is a skill published in the GitHub repository bug-ops/zeph (65 stars, last pushed 11d ago), licensed MIT. It adds 85 tokens to every session and 3,073 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-30.
Other skills, from other repositories
plugin-system
Generic plugin system for Python applications. Auto-discovery, validation, fault tolerance. Zero dependencies (Python stdlib only).
rust-patterns
Idiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices for building safe, performant applications.
rust-testing
Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.
rust-patterns
Idiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices for building safe, performant applications.
rust-check
Run cargo check on the current Rust project to find compile errors.
ax-rust-signature
Use when writing Rust code with axllm for string signatures, field descriptors, JSON schema output, validation, and typed tool argument shapes.