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-feature/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-feature)<a href="https://agentmods.dev/skills/badminton-apps/badman/speckit-maqa-feature"><img src="https://agentmods.dev/badge/skills/badminton-apps/badman/speckit-maqa-feature/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/skills/badminton-apps/badman/speckit-maqa-feature"><img src="https://agentmods.dev/badge/skills/badminton-apps/badman/speckit-maqa-feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 75 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00043 | $0.01260 |
| Opus 5 | $0.00022 | $0.00630 |
| Sonnet 5 | $0.00009 | $0.00252 |
| Haiku 4.5 | $0.00004 | $0.00126 |
Grade A, and why
speckit-maqa-feature scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X PUT \ How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the MAQA Feature Agent. You work on exactly one feature, in exactly one worktree, and report back when done or blocked.
TOON micro-syntax
object: key: value
tabular array: name[N]{f1,f2}:
v1,v2
quote strings containing commas or colons: "val,ue"
Your assignment
$ARGUMENTS
Input arrives in TOON format from the coordinator:
name: <feature-name>
card_id: <trello_card_id or "local">
branch: feature/<feature-name>
worktree: <absolute path to worktree>
task: <one-sentence description>
spec_excerpt: |
<pre-extracted sections from tasks.md, plan.md, spec.md>
checklist[M]{item,item_id}:
<item text>,<item id>
Setup
- All work happens in the
worktreepath. Never touch the main repo directly. - Read
spec_excerpt— this is your authoritative design reference. Do not read spec files yourself. - Read
maqa-config.ymlfrom the worktree to gettest_command,test_file_command, andtdd. - Use the checklist as your step-by-step execution plan.
CONFIG="$WORKTREE/maqa-config.yml"
[ -f "$CONFIG" ] || CONFIG="$WORKTREE/.specify/extensions/maqa/config-template.yml"
cat "$CONFIG" 2>/dev/null | python3 -c "
import sys
cfg = {}
for line in sys.stdin:
line = line.strip()
if ':' in line and not line.startswith('#'):
k, _, v = line.partition(':')
cfg[k.strip()] = v.strip().strip('\"')
print('TEST_CMD=' + cfg.get('test_command', ''))
print('TEST_FILE_CMD=' + cfg.get('test_file_command', ''))
print('TDD=' + cfg.get('tdd', 'false'))
"
Trello real-time ticking (if card_id is not "local")
After completing each checklist item:
curl -s -X PUT \
"https://api.trello.com/1/cards/$CARD_ID/checkItem/$ITEM_ID?state=complete&key=$TRELLO_API_KEY&token=$TRELLO_TOKEN" \
-o /dev/null
If card_id is "local", skip this step.
Implementation cycle
For each checklist item, choose the cycle based on config:
Cycle A — No tests (test_command is empty)
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.
- 4d ago First seen · 170 lines · 43 tokens per session scan A 5a3a1d0cc32f
speckit-maqa-feature is a skill published in the GitHub repository Badminton-Apps/badman (13 stars, last pushed yesterday), licensed Apache-2.0. It adds 43 tokens to every session and 1,260 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
Other skills, from other repositories
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
nw-quality-framework
Quality gates - 11 commit readiness gates, build/test protocol, validation checkpoints, and quality metrics.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
cmux-testing
A regression test for a bug fix ships as two commits so CI proves the test catches the bug.
resolve-issues
Resolves GitHub issues using isolated worktrees and test-driven development, then delegates PR creation to /github:create-pr so the quality gate and the /github:review-pr loop always run. This skill should be used when the user asks to "resolve an issue", "fix issue.
blueprint-derive-tests
Derive test regression plans from git history by finding commits lacking tests. Use when finding untested bug fixes, coverage gaps, or generating a test backlog.