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 striderZA/OpenCodeGameStudios --skill bug-triagegit clone --depth 1 https://github.com/striderZA/OpenCodeGameStudiosWrote 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/striderza/opencodegamestudios/bug-triage)<a href="https://agentmods.dev/skills/striderza/opencodegamestudios/bug-triage"><img src="https://agentmods.dev/badge/skills/striderza/opencodegamestudios/bug-triage/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/striderza/opencodegamestudios/bug-triage"><img src="https://agentmods.dev/badge/skills/striderza/opencodegamestudios/bug-triage.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.00059 | $0.02010 |
| Opus 5.5 | $0.00024 | $0.00804 |
| Sonnet 5.5 | $0.00012 | $0.00402 |
| Haiku 4.5 | $0.00006 | $0.00201 |
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 1mo 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
97% identical to bug-triage — 45 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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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
/team-qacompletes and new bugs have been filed - When the bug count crosses 10+ open items
1. Parse Arguments
Modes:
/bug-triage sprint— triage against the current sprint; assign fixable bugs to the sprint backlog; defer the rest/bug-triage full— full triage of all bugs regardless of sprint scope/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
Glob 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."
Step 2c — Load severity reference
Read docs/framework/coding-standards.md for severity/priority definitions if they
exist. If they do not exist, use the standard definitions in Step 3.
3. Classify Each Bug
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.
- 1mo ago First seen · 244 lines · 59 tokens per session scan A e1505648600d
bug-triage is a skill published in the GitHub repository striderZA/OpenCodeGameStudios (101 stars, last pushed 18d ago), licensed MIT. It adds 59 tokens to every session and 2,010 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to bug-triage, differing in 45 lines, and is treated as a copy.
Other skills, from other repositories
launch-checklist
Complete launch readiness validation covering every department: code, content, store, marketing, community, infrastructure, legal, and go/no-go sign-offs.
milestone-review
Generates a comprehensive milestone progress review including feature completeness, quality metrics, risk assessment, and go/no-go recommendation. Use at milestone checkpoints or when evaluating readiness for a milestone deadline.
bug-report
Creates a structured bug report from a description, or analyzes code to identify potential bugs. Ensures every bug report has full reproduction steps, severity assessment, and context.
release-checklist
Generates a comprehensive pre-release validation checklist covering build verification, certification requirements, store metadata, and launch readiness.
ai-behavior-patterns
Design maintainable AI behavior structures for decision-making, navigation, combat, and systemic interaction.
godot-performance
Profile Godot runtime, scene, rendering, and resource behavior based on representative builds and content.