Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/upex-galaxy/agentic-qa-boilerplatenpx agentmods add skills/upex-galaxy/agentic-qa-boilerplate/sprint-conductorWrote 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/upex-galaxy/agentic-qa-boilerplate/sprint-conductor)<a href="https://agentmods.dev/skills/upex-galaxy/agentic-qa-boilerplate/sprint-conductor"><img src="https://agentmods.dev/badge/skills/upex-galaxy/agentic-qa-boilerplate/sprint-conductor/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/upex-galaxy/agentic-qa-boilerplate/sprint-conductor"><img src="https://agentmods.dev/badge/skills/upex-galaxy/agentic-qa-boilerplate/sprint-conductor.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.00315 | $0.05509 |
| Opus 5.5 | $0.00126 | $0.02204 |
| Sonnet 5.5 | $0.00063 | $0.01102 |
| Haiku 4.5 | $0.00032 | $0.00551 |
Grade A, and why
sprint-conductor 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 2d 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 — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forbidden invocations
NEVER invoke /sdd-* skills from this workflow. SDD is an optional
user-installed ceremony; this skill ships self-contained and does not chain
SDD under any condition. If you need to refactor KATA, fixtures, cli/,
scripts/, or api/schemas/ pipeline, exit this skill first and invoke
/framework-development.
This boundary is mechanical, not advisory: scripts/lint-skills.ts rejects
any /sdd- mention outside this section. See:
.agents/skills/agentic-qa-core/references/skill-composition-strategy.md §4
(governs users who manually install SDD).
Sprint Conductor — one session, a fleet of testers, one screen for the owner
The sprint conductor turns a sprint into a fleet: one sprint-testing worker per ticket, launched the
moment a ticket really reaches the test environment, watched from the Sprint Board instead of from N
terminals. The conductor never tests. It boots the run, keeps the shared state that has exactly one
correct value (tokens, browser states, the sibling repos, the sprint record), decides who runs when,
answers the workers and relays what only the owner can decide.
This skill is thin on purpose. Almost everything it does already has a canonical home, and it points there:
| Concern | Canon |
|---|---|
Fleet mode: worker identity, briefs, launch.txt, rounds, auth one-writer, claims, ad-hoc retest, Live Progress, the dashboard, the sprint record |
sprint-testing/references/fleet-conductor.md |
| The board: commands per stage, the block a worker's brief carries, the four channels, drafts, decision cards, evidence, fixtures, the sentinel wake table, staged artifacts | sprint-testing/references/sprint-board.md, command reference cli/sprint-board/README.md |
| The transport: Run, Tasks, native launch, the mailbox, liveness, closing, the conductor handoff | orca-orchestration (SKILL.md, references/coordinator-playbook.md, references/gotchas.md) |
| The deploy check (the deployed environment is truth, the tracker is a hint) | sprint-testing/references/session-entry-points.md Step 1c |
| This skill: the boot, one watch pass, the round close, the resume | references/boot-and-resume.md, references/watch-pass.md, references/round-close.md |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 271 lines · 315 tokens per session scan A 8c2e7c2ff78f
sprint-conductor is a skill published in the GitHub repository upex-galaxy/agentic-qa-boilerplate (26 stars, last pushed 3d ago), licensed MIT. It adds 315 tokens to every session and 5,509 once invoked, about $0.0013 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-10-26.
Other skills, from other repositories
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
build-evaluate
Verify a completed build against the PRD's anchor case and success criteria. Runs the acceptance test and anchor-case check (serial across drivers sharing a write root), fans out 2-3 read-only cold-read agents (fresh-eyes, anti-scope-creep, drift-vs-mirror). On FAIL, auto-invokes five-whys for root-cause. On PASS with…
finding-reconciliation
Merge the independent A/B/C findings tables into one adjudicated ledger in 07-verification/documentation-verification-report.md — normalizing to the finding schema, deduplicating by location and claim, recording per-finding corroboration without downgrading single-pass findings, promoting cross-pass disagreement to…
scoring-and-release-gate
Score a documentation package against the ten-dimension weighted rubric in references/scorecard-rubric.md with a cited justification per dimension, then evaluate the nineteen conditions in references/release-gate-conditions.md and emit a binary release-ready, conditionally-ready, or not-ready verdict with…
he-eval-report
Generate closure-grade HE eval and drift proof for one execution slice. Use when Linear, milestone, or source-prompt closure needs validation evidence.
he-work
Executes bounded implementation work from approved specs, plans, issues, or small fixes by editing files, running validation, preserving unrelated work, and recording rollback and handoff evidence. Use when asked to implement, execute a plan, apply changes, or build a scoped feature.