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 skills add frabcd/codex-ai-game-studio --skill sprint-statusgit clone --depth 1 https://github.com/frabcd/codex-ai-game-studioWrote 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/frabcd/codex-ai-game-studio/sprint-status)<a href="https://agentmods.dev/skills/frabcd/codex-ai-game-studio/sprint-status"><img src="https://agentmods.dev/badge/skills/frabcd/codex-ai-game-studio/sprint-status/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/frabcd/codex-ai-game-studio/sprint-status"><img src="https://agentmods.dev/badge/skills/frabcd/codex-ai-game-studio/sprint-status.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.00070 | $0.02147 |
| Opus 5 | $0.00035 | $0.01073 |
| Sonnet 5 | $0.00014 | $0.00429 |
| Haiku 4.5 | $0.00007 | $0.00215 |
Grade A, and why
sprint-status 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 5d 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.
This is a copy
91% identical to sprint-status — 32 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Port provenance: adapted from the pinned upstream source at
984023ddac0d5e27624f2baacde6105e45de375funder MIT; see the repository parity ledger for the exact path and blob.
Sprint Status
This is a fast situational awareness check, not a sprint review. It reads the
current sprint plan and story files, scans for status markers, and produces a
concise snapshot in under 30 lines. For detailed sprint management, use
$ai-game-studio:sprint-plan update or $ai-game-studio:milestone-review.
This skill is read-only. It never proposes changes, never asks to write files, and makes at most one concrete recommendation.
1. Find the Sprint
Argument: the first invocation argument (blank = use current sprint)
- If an argument is given (e.g.,
$ai-game-studio:sprint-status 3), searchproduction/sprints/for a file matchingsprint-03.md,sprint-3.md, or similar. Report which file was found. - If no argument is given, find the most recently modified file in
production/sprints/and treat it as the current sprint. - If
production/sprints/does not exist or is empty, report: "No sprint files found. Start a sprint with$ai-game-studio:sprint-plan new." Then stop.
Read the sprint file in full. Extract:
- Sprint number and goal
- Start date and end date
- All story or task entries with their priority (Must Have / Should Have / Nice to Have), owner, and estimate
2. Calculate Days Remaining
Using today's date and the sprint end date from the sprint file, calculate:
- Total sprint days (end minus start)
- Days elapsed
- Days remaining
- Percentage of time consumed
If the sprint file does not include explicit dates, note "Sprint dates not found — burndown assessment skipped."
3. Scan Story Status
First: check for production/sprint-status.yaml.
If it exists, read it directly — it is the authoritative source of truth.
Extract status for each story from the status field. No markdown scanning needed.
Use its sprint, goal, start, end fields instead of re-parsing the sprint plan.
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.
- 5d ago First seen · 211 lines · 70 tokens per session scan A 7e90cb90a60e
sprint-status is a skill published in the GitHub repository frabcd/codex-ai-game-studio (9 stars, last pushed yesterday), licensed MIT. It adds 70 tokens to every session and 2,147 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to sprint-status, differing in 32 lines, and is treated as a copy.
Other skills, from other repositories
manage-taskboard
Manage Codex Taskboard / e-taskboard work with taskctl. Use for taskboard issue IDs, status sync, comments, or taskctl cloud setup—not for unrelated product docs.
workspace
Multi-repo campaign coordinator. Same lifecycle as fleet -- scope claims, discovery relay, wave-based execution -- but the unit of work is a repo, not a file. Coordinates campaigns across repositories with shared context.
decision-map
Turn a loose idea into a git-tracked, session-resumable map of typed investigation tickets, then drive them to resolution one at a time. The planning-loop engine for work that is still being figured out — too fuzzy for a campaign, too big for a single intake item. Resolved tickets graduate into .planning/intake/ for…
merge-review
Reviews pending fleet worktree merges before they're accepted. Reads the merge-check queue, detects file-level conflicts between branches, proposes a safe merge order, and surfaces reconciliation plans for overlapping changes.
unharness
Safely leave Citadel using the active adoption receipt. Produces a no-write, reviewable plan, preserves a portable archive, removes only exact owned material, and reports modified or externally registered surfaces as retained or unknown. Legacy installs must be imported before exact leave is claimed.
negotiation-mindset-and-self
Builds the internal foundation required before entering any negotiation: identity as a negotiator, strategic self-awareness, emotional self-management, assumption auditing, and deliberate style selection. Provides practical self-assessment checklists and pre-negotiation protocols. Use when preparing mentally for a…