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/rockielab/rockie-codex/deploy-teamnpx skills add Rockielab/rockie-codex --skill deploy-teamgit clone --depth 1 https://github.com/Rockielab/rockie-codexWrote 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/rockielab/rockie-codex/deploy-team)<a href="https://agentmods.dev/skills/rockielab/rockie-codex/deploy-team"><img src="https://agentmods.dev/badge/skills/rockielab/rockie-codex/deploy-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.00118 | $0.00965 |
| Opus 5 | $0.00059 | $0.00483 |
| Sonnet 5 | $0.00024 | $0.00193 |
| Haiku 4.5 | $0.00012 | $0.00097 |
Grade A, and why
deploy-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 6d 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.
This is a copy
95% identical to deploy-team — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/deploy-team — configurable agent teams via Codex CLI
Spawns N codex CLI processes in parallel, each with a distinct role prompt,
shared access to a thread, and (optionally) shared context files. Returns a
concatenated report the main agent reads and synthesizes.
When to use a team vs a single subagent
- Single subagent (via native Agent tool): focused, single-responsibility work with a known output shape. Example: "research agent: find 3 recent papers on X and summarize."
- Team (
/deploy-team): multi-perspective work where agents should see each other's findings and challenge them. Example: "gauntlet a new experiment idea — brainstorm, research, attack, validate."
Invocation
python3 .agents/skills/deploy-team/runtime/orchestrator.py \
--template gauntlet \
--topic "should we run the quadratic readout PC control next?" \
[--context matrix-thinking/KILL_LIST.md EXPERIMENT_LOG.md] \
[--max-minutes 15]
Or with a custom config instead of a template:
python3 .agents/skills/deploy-team/runtime/orchestrator.py \
--config path/to/custom-team.json \
--topic "..."
Templates
- gauntlet — 4 agents: brainstormer, researcher, attacker, validator. For: new ideas. The attacker tries to kill; validator checks survivors.
- pre-launch-audit — 3 agents: security, correctness, simplicity. For: reviewing experiment scripts / new code before GPU time.
- post-run-analysis — 3 agents: positive, adversarial, contextualizer. For: interpreting a completed run from multiple angles.
- blog-coherence — 2 agents: style, factual-alignment. For: verifying a new finding doesn't contradict existing site content.
Custom templates live in .agents/skills/deploy-team/templates/*.json.
Run artifacts
Each run creates .team-runs/<run-id>/:
config.json— resolved config (template + topic + context)thread.md— shared append-only thread (agents post findings for peers)context/— symlinked context files agents can readagents/<name>/prompt.txt— the exact prompt sentoutput.md— agent's final written findingsevents.jsonl— raw stream-json events (debug)
REPORT.md— combined report generated by the orchestrator
What ships with it
4 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.
- 6d ago First seen · 90 lines · 118 tokens per session scan A 079cbc52c874
deploy-team is a skill published in the GitHub repository Rockielab/rockie-codex (20 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 118 tokens to every session and 965 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to deploy-team, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…