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 bug-triagegit 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/bug-triage)<a href="https://agentmods.dev/skills/frabcd/codex-ai-game-studio/bug-triage"><img src="https://agentmods.dev/badge/skills/frabcd/codex-ai-game-studio/bug-triage.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.1 | $0.00059 | $0.02135 |
| Opus 5 | $0.00030 | $0.01068 |
| Sonnet 5 | $0.00012 | $0.00427 |
| Haiku 4.5 | $0.00006 | $0.00214 |
Grade A, and why
bug-triage 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 7d 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 bug-triage — 28 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 — 247 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.
Bug Triage
This skill processes the open bug backlog into a prioritised, sprint-assigned action list. It distinguishes between severity (how bad is the impact?) and priority (how urgently must we fix it?), detects systemic trends, and ensures no critical bug is lost between sprints.
Output: production/qa/bug-triage-[date].md
When to run:
- Sprint start — assign open bugs to the new sprint or backlog
- After
$ai-game-studio:team-qacompletes and new bugs have been filed - When the bug count crosses 10+ open items
1. Parse Arguments
Modes:
$ai-game-studio:bug-triage sprint— triage against the current sprint; assign fixable bugs to the sprint backlog; defer the rest$ai-game-studio:bug-triage full— full triage of all bugs regardless of sprint scope$ai-game-studio:bug-triage trend— trend analysis only (no assignment); read-only report- No argument — run sprint mode if a current sprint exists, else full mode
2. Load Bug Backlog
Step 2a — Discover bug files
file discovery for bug reports in priority order:
production/qa/bugs/*.md— individual bug report files (preferred format)production/qa/bugs.md— single consolidated bug log (fallback)- Any
production/qa/qa-plan-*.md"Bugs Found" table (last resort)
If no bug files found:
"No bug files found in
production/qa/bugs/. If bugs are tracked in a different location, adjust the glob pattern. If no bugs exist yet, there is nothing to triage."
Stop and report. Do not proceed if no bugs exist.
Step 2b — Load sprint context
Read the most recently modified file in production/sprints/ to understand:
- Current sprint number / name
- Stories in scope (for assignment target)
- Sprint capacity constraints (if noted)
If no sprint file exists: note "No sprint plan found — assigning to backlog only."
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.
- 7d ago First seen · 247 lines · 59 tokens per session scan A 0c5ca0a8ae7b
bug-triage is a skill published in the GitHub repository frabcd/codex-ai-game-studio (9 stars, last pushed 7d ago), licensed MIT. It adds 59 tokens to every session and 2,135 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 bug-triage, differing in 28 lines, and is treated as a copy.
Other skills, from other repositories
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
systematic-debugging
4-phase root cause analysis: observe, hypothesize, verify, fix. Enforces investigation before any code changes. Emergency stop after 2 failed fixes. Prevents shotgun debugging and fix cascades.
de-vibe
Audit and fix the tells that software was vibe-coded / AI-generated, then give it a small distinctive identity, so it ships looking handcrafted and professional. Use whenever the user says "de-vibe", "does this look AI-generated / vibe coded?", "make this look shippable / handcrafted / professional", "remove the AI…
factory-triage
Triage a Factory work item's issue — trace history, understand architecture, diagnose root cause, then advance the stage.
om-auto-fix-issue
Fix or implement a tracker issue end to end from a single command — takes an issue id or a plain problem description (filed first via om-prepare-issue), classifies, then drives the bug autofix chain (om-verify-in-repo, om-root-cause, om-fix, om-open-pr, om-auto-review-pr, om-auto-qa-pr for UI fixes) or the feature…
status
Display current FIRE project status and validate integrity of intents, work items, and runs.