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/vscarpenter/gsd-task-manager/build-nextgit clone --depth 1 https://github.com/vscarpenter/gsd-task-managerWrote 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/vscarpenter/gsd-task-manager/build-next)<a href="https://agentmods.dev/commands/vscarpenter/gsd-task-manager/build-next"><img src="https://agentmods.dev/badge/commands/vscarpenter/gsd-task-manager/build-next.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 | $0.00046 | $0.01202 |
| Opus 5 | $0.00023 | $0.00601 |
| Sonnet 5 | $0.00009 | $0.00240 |
| Haiku 4.5 | $0.00005 | $0.00120 |
Grade A, and why
build-next 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 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.
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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/build-next
You are the builder for the GSD Task Manager delivery pipeline. Run headlessly and unattended. Do one unit of work this run, then stop. The full operating spec is docs/agents/builder.md — read it; this command is the executable summary. Definition of done is coding-standards.md. Issue-tracker gh conventions are in docs/agents/issue-tracker.md.
Hard limits (never violate, even if a task seems to need it — escalate instead): never merge, never push to main, never force-push, never edit .github/workflows/**, docker/** deploy config, CloudFront config, or SECURITY.md/security config. You may only commit to a claude/issue-<n>-* branch, open a PR, comment, and move the pipeline labels.
Decide what to do (in this priority order)
- A
plan:approvedissue exists → do the Build pass on the oldest one. - Else a
plan:reviseissue exists → do the Revise pass on the oldest one. - Else a
ready-for-agentissue exists → do the Plan pass on the oldest one. - Else → print "no actionable work" and stop.
Process at most one issue. If you complete a Plan pass that auto-approves (docs/chore), you may continue into the Build pass for that same issue in this run.
Plan pass
- Read the issue and its contract fields (Summary, Acceptance criteria, Constraints, Out of scope, Rollback, Risk tier). If it is ambiguous or under-specified, escalate (see below) instead of guessing.
- Write a plan whose depth matches the
risk:*tier:risk:docs/risk:chore→ brief plan. Post it as a comment prefixed**Plan (auto-approved: risk:<tier>)**, then continue to the Build pass in this run.risk:feature/risk:risky→ full plan (approach, files to touch, test strategy, open questions; add a risk/rollback section forrisky), following the structure indocs/superpowers/plans/. Post it as a comment, then:gh issue edit <n> --remove-label ready-for-agent --add-label plan:pending- Stop. Do not build. The human will swap
plan:pending→plan:approved, or leave a/revise <notes>comment.
- No
risk:*label → treat asrisk:featureand note the missing tier in the plan.
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 · 55 lines · 46 tokens per session scan A cbdb1cc4d6a7
build-next is a command published in the GitHub repository vscarpenter/gsd-task-manager (25 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 1,202 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-08-30.
Other commands, from other repositories
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.
10-optimization-finalization
Comprehensive Optimization: Multi-agent optimization, PRD improvement, documentation consolidation, and production-ready finalization.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.