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 story-readinessgit 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/story-readiness)<a href="https://agentmods.dev/skills/frabcd/codex-ai-game-studio/story-readiness"><img src="https://agentmods.dev/badge/skills/frabcd/codex-ai-game-studio/story-readiness/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/story-readiness"><img src="https://agentmods.dev/badge/skills/frabcd/codex-ai-game-studio/story-readiness.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.00077 | $0.03993 |
| Opus 5 | $0.00039 | $0.01997 |
| Sonnet 5 | $0.00015 | $0.00799 |
| Haiku 4.5 | $0.00008 | $0.00399 |
Grade A, and why
story-readiness 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 8d 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
92% identical to story-readiness — 44 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 — 358 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.
Story Readiness
This skill validates that a story file contains everything a developer needs to begin implementation — no mid-sprint design interruptions, no guessing, no ambiguous acceptance criteria. Run it before assigning a story.
This skill is read-only. It never edits story files. It reports findings and asks whether the user wants help filling gaps.
Output: Verdict per story (READY / NEEDS WORK / BLOCKED) with a specific gap list for each non-ready story.
Phase 0: Resolve Review Mode
Resolve the review mode once at startup (store for all gate spawns this run):
- If skill was called with
--review [full|lean|solo]→ use that value - Else read
production/review-mode.txt→ use that value - Else → default to
lean
See the installed Codex role-gate protocol for the full check pattern and mode definitions.
1. Parse Arguments
Scope: the first invocation argument (blank = ask user via the available user-input mechanism)
- Specific path (e.g.,
$ai-game-studio:story-readiness production/epics/combat/story-001-basic-attack.md): validate that single story file. sprint: read the current sprint plan fromproduction/sprints/(most recent file), extract every story path it references, validate each one.all: globproduction/epics/**/*.md, excludeEPIC.mdindex files, validate every story file found.- No argument: ask the user which scope to validate.
If no argument is given, use the available user-input mechanism:
- "What would you like to validate?"
- Options: "A specific story file", "All stories in the current sprint", "All stories in production/epics/", "Stories for a specific epic"
Report the scope before proceeding: "Validating [N] story files."
2. Load Supporting Context
Before checking any stories, load reference documents once (not per-story):
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.
- 8d ago First seen · 358 lines · 77 tokens per session scan A 904b76a14cf2
story-readiness is a skill published in the GitHub repository frabcd/codex-ai-game-studio (10 stars, last pushed 4d ago), licensed MIT. It adds 77 tokens to every session and 3,993 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to story-readiness, differing in 44 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.
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.
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…
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.
belbin-team-roles
Analyzes team composition using Belbin's nine team roles across Thinking, Action, and People categories. Maps team members to roles such as Plant, Shaper, Coordinator, Implementer, and others to identify gaps, overlaps, and imbalances. Use when hiring to fill role gaps, diagnosing recurring team conflicts, auditing…