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/.claude/skills/speckit-maqa-coordinator/SKILL.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/skills/badminton-apps/badman/speckit-maqa-coordinator)<a href="https://agentmods.dev/skills/badminton-apps/badman/speckit-maqa-coordinator"><img src="https://agentmods.dev/badge/skills/badminton-apps/badman/speckit-maqa-coordinator.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00046 | $0.01277 |
| Opus 5 | $0.00023 | $0.00639 |
| Sonnet 5 | $0.00009 | $0.00255 |
| Haiku 4.5 | $0.00005 | $0.00128 |
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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- speckit-maqa — 98% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 152 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.
- 3d ago First seen · 152 lines · 46 tokens per session scan A e538cfd7b46e
speckit-maqa-coordinator is a skill published in the GitHub repository Badminton-Apps/badman (13 stars, last pushed yesterday), licensed Apache-2.0. It adds 46 tokens to every session and 1,277 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
scaffold-dotnet-test-project
MUST USE when an existing .NET test project was excluded from a .slnf/CI solution filter, disappeared from .sln/.slnx discovery, or lost its production ProjectReference; also for requests to set up, create, reuse, add, register, include, or repair a test project. Handles "tests pass directly but CI discovers zero"…
cy-execute-task
Implement and verify an existing CompozyOS spec task, then update its tracking. Excludes review remediation.
team-qa
Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package for a sprint or feature. Covers: test plan generation, test case writing, smoke check gate, manual QA execution, and sign-off report.
gh-issue
Size-audit, write, and split BanyanDB issues that somebody else or an automated TDD workflow can implement. Use whenever the user asks to file or revise an issue, decide whether an issue is too large, make an issue TDD-ready, turn a design into tickets, or split an umbrella into executable leaves. Do not draft or file…
implement-feature
Implement an approved feature plan with fresh-context slices, TDD, evidence, and PR-ready output.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.