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/frabcd/codex-ai-game-studio/day-one-patchnpx skills add frabcd/codex-ai-game-studio --skill day-one-patchgit 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/day-one-patch)<a href="https://agentmods.dev/skills/frabcd/codex-ai-game-studio/day-one-patch"><img src="https://agentmods.dev/badge/skills/frabcd/codex-ai-game-studio/day-one-patch.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.00063 | $0.02180 |
| Opus 5 | $0.00032 | $0.01090 |
| Sonnet 5 | $0.00013 | $0.00436 |
| Haiku 4.5 | $0.00006 | $0.00218 |
Grade A, and why
day-one-patch 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 4d 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 — 229 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.
Day-One Patch
Every shipped game has a day-one patch. Planning it before launch day prevents chaos. This skill scopes the patch to only what is safe and necessary, gates it through a lightweight QA pass, and ensures a rollback plan exists before anything ships. It is a mini-sprint — not a hotfix, not a full sprint.
When to run:
- After the gold master build is locked (cert approved or launch candidate tagged)
- When known bugs exist that are too risky to address in the gold master
- When cert feedback requires minor fixes post-submission
- When a pre-launch playtest surfaces must-fix issues after the release gate passed
Day-one patch scope rules:
- Only P1/P2 bugs that are SAFE to fix quickly
- No new features — this is fix-only
- No refactoring — minimum viable change
- Any fix that requires more than 4 hours of dev time belongs in patch 1.1, not day-one
Output: production/releases/day-one-patch-[version].md
Phase 1: Load Release Context
Read:
production/stage.txt— confirm project is in Release stage- The most recent file in
production/gate-checks/— read the release gate verdict production/qa/bugs/*.md— load all bugs with Status: Open or Fixed — Pending Verificationproduction/sprints/most recent — understand what shippedproduction/security/security-audit-*.mdmost recent — check for any open security items
If production/stage.txt is not Release or Polish:
"Day-one patch prep is for Release-stage projects. Current stage: [stage]. This skill is not appropriate until you are approaching launch."
Phase 2: Scope the Patch
Step 2a — Classify open bugs for patch inclusion
For each open bug, evaluate:
| Criterion | Include in day-one? |
|---|---|
| S1 or S2 severity | Yes — must include if safe to fix |
| P1 priority | Yes |
| Fix estimated < 4 hours | Yes |
| Fix requires architecture change | No — defer to 1.1 |
| Fix introduces new code paths | No — too risky |
| Fix is data/config only (no code change) | Yes — very low risk |
| Cert feedback requirement | Yes — required for platform approval |
| S3/S4 severity | Only if trivial config fix; otherwise defer |
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.
- 4d ago First seen · 229 lines · 63 tokens per session scan A f16cb9d369de
day-one-patch is a skill published in the GitHub repository frabcd/codex-ai-game-studio (8 stars, last pushed 4d ago), licensed MIT. It adds 63 tokens to every session and 2,180 once invoked, about $0.0003 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-31.
Other skills, from other repositories
triage
Apply a formal state machine to issues — assign category (bug/enhancement/question/spike) and state (needs-triage → needs-info → ready-for-agent → ready-for-human → wontfix). Issues marked ready-for-agent become inputs to supergraph:plan. Use when processing a backlog, reviewing new issues, or preparing work for…
frappe-gameplan
Frappe Gameplan guidance for team discussions, projects, tasks, notes, decisions, async collaboration, permissions, and workspace workflows. Use when work touches Gameplan or planning/collaboration features in the Frappe ecosystem.
forge-workflow
Helps an organization admin manage custom Forge workflows conversationally — both AUTHORING new workflows and DELETING existing org- or team-scoped overrides. Invoke this skill whenever the user asks to "create a workflow", "customize my SDLC", "build a new workflow", "set up a custom process", "author a workflow"…
forge-autopilot
Routes any product, engineering, or software development lifecycle (SDLC/PDLC) activity to Forge. Invoke this skill whenever the user describes work that involves the product development process — across any phase: discovery, definition, planning, execution, review, handoff, release, or reporting. This includes…
setup-matt-pocock-skills
Configure repository-wide Matt Engineering tracker, triage, domain-doc, and Wayfinding conventions. Use only when the user explicitly selects Setup to initialize Matt workflows.
to-tickets
Break a plan, spec, or established conversation into implementable tracer-bullet tickets with explicit blocking edges. Use when the user asks to split work into tickets, issues, or independently executable slices.