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 commands/kellvembarbosa/team-orchestrator/devops-engineergit clone --depth 1 https://github.com/kellvembarbosa/team-orchestratorWhat 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 | $0.00008 | $0.00128 |
| Opus 5 | $0.00004 | $0.00064 |
| Sonnet 5 | $0.00002 | $0.00026 |
| Haiku 4.5 | $0.00001 | $0.00013 |
Grade A, and why
devops-engineer 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 2d 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
80% identical to accessibility-analyst — 6 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.
What it actually says
Spawn an agent team named "devops-engineer" using the stored team definition.
- Read the team configuration from
${CLAUDE_PLUGIN_ROOT}/teams/devops-engineer.md. Frontmatter may includemodelandsizehints; body holds the team's instructions. - Create an agent team that follows those instructions. Honor
modelandsizehints if present. - Incorporate this additional user context into the spawn prompt (may be empty): $ARGUMENTS
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.
- 2d ago First seen · 12 lines · 8 tokens per session scan A f280a1585ac6
devops-engineer is a command published in the GitHub repository kellvembarbosa/team-orchestrator (4 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 8 tokens to every session and 128 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 80% identical to accessibility-analyst, differing in 6 lines, and is treated as a copy.
Other commands, from other repositories
context
项目上下文管理：初始化 .context 目录、记录决策日志、压缩归档、查看历史.
update-workflow
Regenerate an existing custom workflow's shortcut command wiring from the current swarm template.
greptile-review
Execute the full Greptile review cycle on a PR, looping until score meets threshold or circuit breaker triggers.
bugfix
TDD-driven bugfix workflow: tester writes failing test (RED) → developer fixes (GREEN) → developer refactors (REFACTOR) → reviewer validates. Accepts issue number, description, or both. Auto-creates PR unless --no-pr flag is passed.
dev-task
Create an agent team to develop: Developer teammate + Code-tester teammate + QA-tester teammate + Reviewer teammate + Researcher subagent → implements .dev/cdt/plans/plan-$TIMESTAMP.md in waves.
Team: Dev Loop
Spawn an implementer + verifier (+ optional planner) team that iterates on a scoped change until a deterministic check passes. Lead stays light.