Borrowing it
Nothing to install: this file belongs to vscarpenter/gsd-task-manager. 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/vscarpenter/gsd-task-manager/main/.agents/skills/source-command-build-next/SKILL.mdgit 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/skills/vscarpenter/gsd-task-manager/source-command-build-next)<a href="https://agentmods.dev/skills/vscarpenter/gsd-task-manager/source-command-build-next"><img src="https://agentmods.dev/badge/skills/vscarpenter/gsd-task-manager/source-command-build-next/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/vscarpenter/gsd-task-manager/source-command-build-next"><img src="https://agentmods.dev/badge/skills/vscarpenter/gsd-task-manager/source-command-build-next.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 Excessive Agency · line 25 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 31 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00048 | $0.01234 |
| Opus 5.5 | $0.00019 | $0.00494 |
| Sonnet 5.5 | $0.00010 | $0.00247 |
| Haiku 4.5 | $0.00005 | $0.00123 |
Grade A, and why
source-command-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 2mo 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
source-command-build-next
Use this skill when the user asks to run the migrated source command build-next.
Command Template
/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 Codex/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.
- 2mo ago First seen · 61 lines · 48 tokens per session scan A fa3d27313f60
source-command-build-next is a skill published in the GitHub repository vscarpenter/gsd-task-manager (40 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 1,234 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-08-30.
Other skills, from other repositories
report-issue
File a bug or feature request against this repository (cyanheads/git-mcp-server) using the gh CLI. Use for tool logic bugs, git provider misbehavior, transport issues, auth/config problems, or new feature proposals.
papi-build
Invoke when executing a build via buildexecute. Covers branching, gestalt pre-build check, and post-build audit.
gitlab-discovery
Find a GitLab project or namespace and establish the exact target for follow-up repository, merge request, work-item or CI work. Use for GitLab project discovery, not local filesystem search or GitHub repositories.
papi-auto
Continue an approved PAPI cycle through implementation, verification and review using bounded autonomy. Resume durable work without rebuilding it; propose new scope before persisting it.
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
tuturuuu-agent-coordination
Coordinate Tuturuuu multi-agent programs, exact-head evidence, shared-worktree ownership, and handoffs.