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/team)<a href="https://agentmods.dev/commands/cfvillarroel/carryover/team"><img src="https://agentmods.dev/badge/commands/cfvillarroel/carryover/team.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.1 | $0.00017 | $0.00421 |
| Opus 5 | $0.00009 | $0.00211 |
| Sonnet 5 | $0.00003 | $0.00084 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
team 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 7d 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
Assemble and drive a team of Conductor workspaces. A team is a named roster mapping each member
workspace to a role (e.g. lead, frontend, backend, reviewer). $ARGUMENTS is free-form intent
(e.g. "make a team checkout-revamp with paris as frontend and zurich as backend, then have each start").
Use the co-mem team CLI via Bash (resolve the headroom venv python so writes succeed):
PY="$HOME/.headroom/venv/bin/python"; [ -x "$PY" ] || PY="$(command -v python3)"
"$PY" "$HOME/.carryover/co-mem" team list # show teams + rosters
"$PY" "$HOME/.carryover/co-mem" team add <team> <workspace> <role>
"$PY" "$HOME/.carryover/co-mem" team rm <team> [<workspace>] # drop a member, or the whole team
"$PY" "$HOME/.carryover/co-mem" team send <team> [@role] "<message>" # notify (passive)
"$PY" "$HOME/.carryover/co-mem" team assign <team> [@role] "<task>" # handover: notify + "execute now"
As the lead, when dispatching real work: decompose the goal into per-role tasks yourself, then
assign each role its own slice (role-specific assign <team> @frontend "…") rather than blasting the
same message to everyone. Address members by their city codename or project name (stable).
Manage teams visually in the dashboard (co-dash → 👥 Teams tab). Note: assign notifies idle
workspaces but can't wake them — a teammate picks up its task when its workspace is next opened.
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.
- 7d ago First seen · 26 lines · 17 tokens per session scan A deb9575f9084
team is a command published in the GitHub repository Cfvillarroel/carryover (5 stars, last pushed 22d ago), licensed MIT. It adds 17 tokens to every session and 421 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
status
Display project status, active tracks, and next actions.
implement
Execute tasks from a track's implementation plan following TDD workflow.
new-track
Create a new track with specification and phased implementation plan.
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.