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/say)<a href="https://agentmods.dev/commands/cfvillarroel/carryover/say"><img src="https://agentmods.dev/badge/commands/cfvillarroel/carryover/say/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/say"><img src="https://agentmods.dev/badge/commands/cfvillarroel/carryover/say.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.00008 | $0.00153 |
| Opus 5 | $0.00004 | $0.00077 |
| Sonnet 5 | $0.00002 | $0.00031 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade A, and why
say 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 9d 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
Send a message to every workspace connected to this one (set up with /connect). $ARGUMENTS =
the message.
Run via Bash (resolve the headroom venv python so the write succeeds):
PY="$HOME/.headroom/venv/bin/python"; [ -x "$PY" ] || PY="$(command -v python3)"
"$PY" "$HOME/.carryover/co-mem" say <message>
Substitute <message> from the arguments, escaping it safely. It reports which workspaces received
it. If this workspace isn't connected to any other, the command errors — tell the user to run
/connect <workspace> first.
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.
- 9d ago First seen · 18 lines · 8 tokens per session scan A 60d78af961fb
say is a command published in the GitHub repository Cfvillarroel/carryover (5 stars, last pushed 24d ago), licensed MIT. It adds 8 tokens to every session and 153 once invoked, about $0.0000 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
implement
Execute tasks from a track's implementation plan following TDD workflow.
new-track
Create a new track with specification and phased implementation plan.
status
Display project status, active tracks, and next actions.
team-delegate
Task delegation dashboard for managing team workload, assignments, and rebalancing.
team-status
Display team members, task status, and progress for an active agent team.
manage
Manage track lifecycle: archive, restore, delete, rename, and cleanup.