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.
git clone --depth 1 https://github.com/Cfvillarroel/carryoverWrote 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/commands/cfvillarroel/carryover/handoff)<a href="https://agentmods.dev/commands/cfvillarroel/carryover/handoff"><img src="https://agentmods.dev/badge/commands/cfvillarroel/carryover/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/commands/cfvillarroel/carryover/handoff"><img src="https://agentmods.dev/badge/commands/cfvillarroel/carryover/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.00013 | $0.00240 |
| Opus 5 | $0.00006 | $0.00120 |
| Sonnet 5 | $0.00003 | $0.00048 |
| Haiku 4.5 | $0.00001 | $0.00024 |
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 8d 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
Hand off the current task/context to another Conductor workspace. $ARGUMENTS = the target
workspace name (optionally followed by a note about what to hand off).
Write a concise handoff summary yourself, from this session's context. Include:
- what was done,
- the current state,
- what remains / what you're asking the other workspace to do,
- key files, decisions, or gotchas they'll need to continue.
Then send it via Bash (resolve the headroom venv python so the write works):
PY="$HOME/.headroom/venv/bin/python"; [ -x "$PY" ] || PY="$(command -v python3)"
"$PY" "$HOME/.carryover/co-mem" send <workspace> "<your handoff summary>"
Substitute <workspace> and your summary, escaping it safely. Confirm to the user what you handed
off and to whom. If no workspace was given, ask which one (or run
python3 "$HOME/.carryover/co-mem" connections to see connected ones).
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.
- 8d ago First seen · 24 lines · 13 tokens per session scan A 661c9d5c00f8
handoff is a command published in the GitHub repository Cfvillarroel/carryover (5 stars, last pushed 24d ago), licensed MIT. It adds 13 tokens to every session and 240 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 commands, from other repositories
cost-optimize
You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, GCP, and OCI. Where provider-specific code appears below, adapt…
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
performance-optimization
Orchestrate end-to-end application performance optimization from profiling to monitoring.
refactor-clean
You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.
revert
Git-aware undo by logical work unit (track, phase, or task).
status
Display project status, active tracks, and next actions.