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 hoatv2211/GameStudio-CodexKIT --skill audio-content-pipeline-reviewgit clone --depth 1 https://github.com/hoatv2211/GameStudio-CodexKITWrote 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/hoatv2211/gamestudio-codexkit/audio-content-pipeline-review)<a href="https://agentmods.dev/skills/hoatv2211/gamestudio-codexkit/audio-content-pipeline-review"><img src="https://agentmods.dev/badge/skills/hoatv2211/gamestudio-codexkit/audio-content-pipeline-review/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/hoatv2211/gamestudio-codexkit/audio-content-pipeline-review"><img src="https://agentmods.dev/badge/skills/hoatv2211/gamestudio-codexkit/audio-content-pipeline-review.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.00055 | $0.00841 |
| Opus 5 | $0.00028 | $0.00420 |
| Sonnet 5 | $0.00011 | $0.00168 |
| Haiku 4.5 | $0.00006 | $0.00084 |
Grade A, and why
audio-content-pipeline-review 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 11d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- studio-production-planning — 86% identical, 34 lines differ
- product-analytics-experiment-review — 83% identical, 30 lines differ
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audio Content Pipeline Review
Overview
Provide an evidence-first contract for audio source, loudness, codec, streaming, looping, localization, routing, middleware, memory, concurrency, and platform limits.
When to use
Use only for the trigger conditions in the description and when the requested artifact needs explicit owners, evidence, limitations, and verification.
When NOT to use
Do not use for broad frame-time budgeting without audio pipeline evidence.
Required inputs and context discovery
Collect exact project and build identity, requested scope, owners, dependencies, constraints, existing evidence, commands, artifact paths, risks, approvals, rollback or recovery, and unavailable information.
Safety and risk level
Risk level is read-only. Read-only review never authorizes mutation. Any load, rollout, publication, service, database, credential, or external-system action requires explicit human approval and bounded stop conditions.
Workflow
- Bind source audio, rights, owner, target event, platform, and middleware version. Completion criterion: evidence is recorded and unresolved items are explicit.
- Check sample rate, channels, loudness, peaks, silence, loops, and edit boundaries. Completion criterion: evidence is recorded and unresolved items are explicit.
- Review codec, quality, streaming, preload, memory, concurrency, ducking, and routing. Completion criterion: evidence is recorded and unresolved items are explicit.
- Trace localization, subtitles, fallback, event references, and generated banks. Completion criterion: evidence is recorded and unresolved items are explicit.
- Return evidence-backed issues with audible reproduction and validation targets. Completion criterion: evidence is recorded and unresolved items are explicit.
Evidence and output contract
Produce audio-pipeline-review.json with scope, snapshot, findings, owners, commands and exit codes, artifacts, acceptance criteria, Verified facts, Snapshot assumptions, Unverified hypotheses, BLOCKED items, and next actions.
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.
- 11d ago First seen · 79 lines · 55 tokens per session scan A b470f741e553
audio-content-pipeline-review is a skill published in the GitHub repository hoatv2211/GameStudio-CodexKIT (3 stars, last pushed 4d ago), licensed MIT. It adds 55 tokens to every session and 841 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
deep-discovery
Use when the user asks for deep discovery, 100-question brainstorming, idea interrogation, architecture stress testing, strategy vetting, weakness finding, hole-poking, exhaustive exploration, planning or auditing Codex plugins or skills, or pre-commitment review of a design, plan, strategy, architecture, product…
prewalk
Use when the user wants a coding task executed with a strong planner model first and a faster/cheaper executor model after the first successful implementation edit.
code-standards
C# coding standards and code review. Use when the user mentions coding standards or conventions, writing code to spec, defining standards for a project, cohesion and coupling, design pattern selection, or naming conventions, or wants a code review on the design and standards dimension.
registry-broker-orchestrator
Use Registry Broker to discover and summon specialist agents for focused subtasks from inside Codex.
unity-performance
Unity performance optimization. Use when the user asks to optimize a class, view, function, folder or an entire module, or mentions stutter, lag, frame drops, low FPS, jank, overheating, battery drain, GC allocation, memory leaks, DrawCalls, batching, overdraw, slow loading, large build size, Profiler, PerfDog, or…
sega
A playful, arcade-inspired interface for games — built on the VT323 pixel typeface, hard-edged 0px corners, chunky pill buttons that physically press into solid offset blocks.