Borrowing it
Nothing to install: this file belongs to Badminton-Apps/badman. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Badminton-Apps/badman/develop/.specify/extensions/maqa/commands/speckit.maqa.coordinator.mdgit clone --depth 1 https://github.com/Badminton-Apps/badmanWrote 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/badminton-apps/badman/speckit.maqa.coordinator)<a href="https://agentmods.dev/commands/badminton-apps/badman/speckit.maqa.coordinator"><img src="https://agentmods.dev/badge/commands/badminton-apps/badman/speckit.maqa.coordinator/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/badminton-apps/badman/speckit.maqa.coordinator"><img src="https://agentmods.dev/badge/commands/badminton-apps/badman/speckit.maqa.coordinator.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.00038 | $0.01224 |
| Opus 5.5 | $0.00015 | $0.00490 |
| Sonnet 5.5 | $0.00008 | $0.00245 |
| Haiku 4.5 | $0.00004 | $0.00122 |
Grade A, and why
speckit.maqa.coordinator 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the MAQA coordinator. You orchestrate parallel feature agents and QA agents across the full spec workflow.
Step 1 — Read config
Read maqa-config.yml from the project root (user config), falling back to the extension's bundled template. Extract: max_parallel, worktree_base, test_command, tdd, board.
CONFIG_FILE="maqa-config.yml"
[ -f "$CONFIG_FILE" ] || CONFIG_FILE=".specify/extensions/maqa/config-template.yml"
cat "$CONFIG_FILE"
Detect active board tool. Check board: field in config first; if auto or absent, probe installed companions in this order:
BOARD="local"
BOARD_CONFIG=$(python3 -c "
import re
cfg = {}
try:
for line in open('$CONFIG_FILE'):
m = re.match(r'^board:\s*\"?([^\"#\n]+)\"?', line.strip())
if m: cfg['board'] = m.group(1).strip()
except: pass
print(cfg.get('board','auto'))
")
if [ "$BOARD_CONFIG" != "auto" ] && [ -n "$BOARD_CONFIG" ]; then
BOARD="$BOARD_CONFIG"
else
[ -f "maqa-trello/trello-config.yml" ] && [ -n "$TRELLO_API_KEY" ] && BOARD="trello"
[ -f "maqa-linear/linear-config.yml" ] && [ -n "$LINEAR_API_KEY" ] && BOARD="linear"
[ -f "maqa-github-projects/github-projects-config.yml" ] && { [ -n "$GH_TOKEN" ] || gh auth token &>/dev/null; } && BOARD="github-projects"
[ -f "maqa-jira/jira-config.yml" ] && [ -n "$JIRA_API_TOKEN" ] && BOARD="jira"
[ -f "maqa-azure-devops/azure-devops-config.yml" ] && [ -n "$AZURE_DEVOPS_TOKEN" ] && BOARD="azure-devops"
fi
echo "board: $BOARD"
Detect CI gate:
CI_GATE="none"
[ -f "maqa-ci/ci-config.yml" ] && CI_GATE="enabled"
echo "ci_gate: $CI_GATE"
Step 2 — Discover specs
python3 - <<'EOF'
import os, glob, json
specs = []
for path in sorted(glob.glob('specs/*/spec.md')):
name = os.path.basename(os.path.dirname(path))
has_tasks = os.path.exists(f'specs/{name}/tasks.md')
has_plan = os.path.exists(f'specs/{name}/plan.md')
specs.append({'name': name, 'has_tasks': has_tasks, 'has_plan': has_plan})
print(json.dumps(specs, indent=2))
EOF
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.
- 1mo ago First seen · 146 lines · 38 tokens per session scan A 553c319f29b6
speckit.maqa.coordinator is a command published in the GitHub repository Badminton-Apps/badman (13 stars, last pushed 2d ago), licensed Apache-2.0. It adds 38 tokens to every session and 1,224 once invoked, about $0.0002 per session on Opus 5.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-09-04.
Other commands, from other repositories
implement
Execute tasks from a track's implementation plan following TDD workflow.
workflow-implement
Exécuter la phase d'Implémentation - développement sprint avec TDD/BDD.
rules
A command for managing coding rules stored in CLAUDE.md, AGENTS.md, and optional project RULES.md files. It can select built-in rules, add personal rules, change settings such as architecture or coverage, and control whether test-driven development (TDD) is required.
execute-work-packet
Execute a single work packet: verify dependencies, run TDD task loop through three gates, write completion marker.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
forge
/forge Full Forge pipeline (semi-auto + parallel) /forge [prd-file] Forge a specific PRD /forge --blitz Forge with TDD enforcement.