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/fatihkan/badiWrote 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/fatihkan/badi/team)<a href="https://agentmods.dev/commands/fatihkan/badi/team"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/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.00000 | $0.02367 |
| Opus 5 | $0.00000 | $0.01184 |
| Sonnet 5 | $0.00000 | $0.00473 |
| Haiku 4.5 | $0.00000 | $0.00237 |
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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Virtual eng team orchestrator. Runs a goal end-to-end through the whole team — strategy → plan → build → QA → ship — conducted by the engineering-manager, delegating to every specialist. One entry point that connects /ceo-review, /eng-review, /qa, and /ship.
Required Tools
- Read (goal, specs, memory, task board)
- Grep / Glob (map the affected surface)
- Bash (git, tests, build)
- Agent (delegate to the managerial roles + specialists — held by the main thread only)
- AskUserQuestion (the ship gate in Step 5; scope choices)
- Write / Edit (the main thread implements increments and records to the daily note / task board)
When to Use
When you want the full virtual engineering team on a feature or goal, not just one role. /team "<goal>" runs the entire pipeline. For a single stage, call the role command directly (/ceo-review, /eng-review, /qa, /ship).
The Team
| Stage | Role / Agent | Command it mirrors |
|---|---|---|
| Conductor (all stages) | the main thread — holds the Agent tool; performs every delegation and executes the delegation map | this command |
| Strategy gate | product-strategist | /ceo-review |
| Plan & sequence | engineering-manager — authors the plan and the delegation map | /eng-review |
| Build | implementer: the main thread (default) or a write-capable agent named in the map; advisory reviewers (read-only): architecture-advisor, security-scanner, test-strategist, refactoring-advisor, performance-profiler, … | — |
| Quality gate | qa-lead | /qa |
| Ship gate | the user, via AskUserQuestion | — |
| Release | release-manager | /ship |
Who conducts. The summary line above says the run is "conducted by the engineering-manager"; read that as: the engineering-manager writes the score — the locked approach, the increments, and the delegation map — but it has no Agent tool and cannot launch anyone. The main thread conducts: it holds the Agent tool, launches every brief in Steps 1–4 and 6 (Step 5 is a question to the user, not a brief), and executes the map the engineering-manager produced.
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.
- today First seen · 107 lines · 0 tokens per session scan A dda11c9dab05
team is a command published in the GitHub repository fatihkan/badi (7 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,367 tokens. 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-09-06.
Other commands, from other repositories
plan-start
5-phase planning command: PRD analysis, design review, technical decisions, dynamic research team, metrics. Produces a complete implementation plan + ADRs before any code is written.
plan-ceo-review
Strategic product gate — challenge the brief, find the 10-star product hiding inside the request, before writing any code.
routines-discover
Analyzes the current project to surface high-value Routines use cases across the three trigger types (schedule, API, GitHub events). Usage: /routines-discover.
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524) — sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
review-pr
Perform a comprehensive code review of a pull request.
git-worktree-clean
Clean up stale git worktrees with merged branch detection and disk usage report.