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 skills/friedbotstudio/baseline/sprint-oraclenpx skills add friedbotstudio/baseline --skill sprint-oraclegit clone --depth 1 https://github.com/friedbotstudio/baselineWrote 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/friedbotstudio/baseline/sprint-oracle)<a href="https://agentmods.dev/skills/friedbotstudio/baseline/sprint-oracle"><img src="https://agentmods.dev/badge/skills/friedbotstudio/baseline/sprint-oracle.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.00096 | $0.00809 |
| Opus 5 | $0.00048 | $0.00404 |
| Sonnet 5 | $0.00019 | $0.00162 |
| Haiku 4.5 | $0.00010 | $0.00081 |
Grade A, and why
sprint-oracle 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.
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sprint-oracle — mechanical completeness gate for a sprint
sprint-oracle reads a sprint manifest (authored by sprint-plan), scans the test tree for the @sprint-feature / @kind tags, and reports whether every feature is complete. It is the answer to "the final system ships incomplete": a sprint is not done until the oracle exits 0. Read-only — it reports, it never edits.
What it checks (per feature)
A feature is complete only when all three hold:
- done-record —
done_recordis non-empty (the feature traces to a spec AC). - edge — at least one name in
edge_testsresolves to a test tagged// @sprint-feature:<id> @kind:edge. - wiring —
wiring_testresolves to a test tagged// @sprint-feature:<id> @kind:wiring.
"Resolves" means: the named test exists in a scanned .mjs file and its tag's feature id and kind match. A test tagged @kind:happy never satisfies an edge or wiring requirement — the happy path does not count as completion.
Exit codes (fail loud, fail distinct)
| Code | Meaning |
|---|---|
0 |
every feature complete (or the manifest has zero features — vacuously complete) |
2 |
gaps found — at least one feature is missing a dimension; a per-feature gap list is printed to stderr |
1 |
operational error — the manifest could not be read or parsed (distinct from a completeness gap) |
A gap is {feature, dimension, detail} where dimension is one of done-record / edge / wiring, and detail names the unresolved test(s).
How to use
node .claude/skills/sprint-oracle/oracle.mjs <manifest-path> [test-root]
test-root defaults to tests. The CLI prints each gap as GAP <feature>: <dimension> — <detail> and exits with the code above. For programmatic use, import runOracle({manifestPath, testRoot}) → {code, gaps, error?}.
Example gap output:
GAP search: edge — no resolvable @kind:edge test among [search_empty_query]
GAP search: wiring — wiring_test 'search_end_to_end' does not resolve to a @kind:wiring test
What ships with it
1 file 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.
- 3d ago First seen · 56 lines · 96 tokens per session scan A d16f1c9961e0
sprint-oracle is a skill published in the GitHub repository friedbotstudio/baseline (11 stars, last pushed 7d ago), licensed Apache-2.0. It adds 96 tokens to every session and 809 once invoked, about $0.0005 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 skills, from other repositories
probe
Report this absolute source path, then read the nested routine.
dev-standards
Enforces development workflows, quality gates, coding standards, and release processes for the deterministic-agent-control-protocol project. Use when implementing features, fixing bugs, refactoring architecture, adding integrations, updating policies, writing tests, updating documentation, or preparing releases.
brainstorming
The Socratic spec-refinement front of /feature, and the planning front of /sprint. Routed to BEFORE any code — it takes a one-line idea and drives it to an approved, concrete spec with testable acceptance criteria. Five gated phases — frame, shape, refine, write, review-and-approve. No implementation and no handoff to…
commit-gate
The only path to a commit. Routed to when the user invokes /commit or otherwise instructs codeArbiter to persist staged changes. Nine gated phases — permission, branch, classification, verification (test/lint/secrets), behavioral proof, diff review, selective stage, message, commit. Nothing reaches version control…
context-check
Optional manual drift audit — report stale provenance-tracked docs (via provenancelib drift detection across .codearbiter/.provenance/), then per stale doc offer re-scout / re-baseline / defer. Not the daily loop; commit-gate auto-heal owns routine maintenance.
context-creation
The brownfield back-fill. Routed to by /create-context, and by startup when .codearbiter/CONTEXT.md lacks the body marker but source code exists. Six gated phases — pre-flight, scout dispatch, synthesis, gap interview, write, lock. Reads the existing codebase through parallel scouts, drafts every surviving…