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 architecture-decisiongit 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/architecture-decision)<a href="https://agentmods.dev/skills/frabcd/codex-ai-game-studio/architecture-decision"><img src="https://agentmods.dev/badge/skills/frabcd/codex-ai-game-studio/architecture-decision/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/architecture-decision"><img src="https://agentmods.dev/badge/skills/frabcd/codex-ai-game-studio/architecture-decision.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.00036 | $0.04654 |
| Opus 5 | $0.00018 | $0.02327 |
| Sonnet 5 | $0.00007 | $0.00931 |
| Haiku 4.5 | $0.00004 | $0.00465 |
Grade A, and why
architecture-decision 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
84% identical to architecture-decision — 54 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 — 459 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.
When this skill is invoked:
0. Parse Arguments — Detect Retrofit Mode
Resolve the review mode (once, store for all gate spawns this run):
- If
--review [full|lean|solo]was passed → use that - 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.
If the argument starts with retrofit followed by a file path
(e.g., $ai-game-studio:architecture-decision retrofit docs/architecture/adr-0001-event-system.md):
Enter retrofit mode:
- Read the existing ADR file completely.
- Identify which template sections are present by scanning headings:
## Status— BLOCKING if missing:$ai-game-studio:story-readinesscannot check ADR acceptance## ADR Dependencies— HIGH if missing: dependency ordering breaks## Engine Compatibility— HIGH if missing: post-cutoff risk unknown## GDD Requirements Addressed— MEDIUM if missing: traceability lost
- Present to the user:
## Retrofit: [ADR title] File: [path] Sections already present (will not be touched): ✓ Status: [current value, or "MISSING — will add"] ✓ [section] Missing sections to add: ✗ Status — BLOCKING (stories cannot validate ADR acceptance without this) ✗ ADR Dependencies — HIGH ✗ Engine Compatibility — HIGH - Ask: "Shall I add the [N] missing sections? I will not modify any existing content."
- If yes:
- For Status: ask the user — "What is the current status of this decision?" Options: "Proposed", "Accepted", "Deprecated", "Superseded by ADR-XXXX"
- For ADR Dependencies: ask — "Does this decision depend on any other ADR? Does it enable or block any other ADR or epic?" Accept "None" for each field.
- For Engine Compatibility: read the engine reference docs (same as Step 1 below) and ask the user to confirm the domain. Then generate the table with verified data.
- For GDD Requirements Addressed: ask — "Which GDD systems motivated this decision? What specific requirement in each GDD does this ADR address?"
- Append each missing section to the ADR file using the available file-editing mechanism.
- Never modify any existing section. Only append or fill absent sections.
- After adding all missing sections, update the ADR's
## Datefield if it is absent. - Suggest: "Run
$ai-game-studio:architecture-reviewto re-validate coverage now that this ADR has its Status and Dependencies fields."
If NOT in retrofit mode, proceed to Step 1 below (normal ADR authoring).
No-argument guard: If no argument was provided (title is empty), ask before running Phase 0:
"What technical decision are you documenting? Please provide a short title (e.g.,
event-system-architecture,physics-engine-choice)."
Use the user's response as the title, then proceed to Step 1.
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 · 459 lines · 36 tokens per session scan A fc4de54ed23f
architecture-decision is a skill published in the GitHub repository frabcd/codex-ai-game-studio (9 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 4,654 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to architecture-decision, differing in 54 lines, and is treated as a copy.
Other skills, from other repositories
watch
File sentinel that monitors the working directory for changes and marker comments, then auto-triggers appropriate skills. Poll-based via git diff against the last scan commit. Writes intake items for batch processing and routes marker actions through /do. Use for automatic reactions to file changes; do NOT use for…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
marshal
Meta-orchestrator that takes any direction — broad, specific, or vague — and autonomously chains skills and context into actionable work. Gathers context from codebase, docs, and memory. Only asks the user when it genuinely cannot proceed. Single-session orchestrator.
wiki
Markdown-first knowledge base where the LLM acts as librarian. Ingests raw sources, compiles and interlinks topic files, self-maintains an index. No vector DB or embeddings required -- uses LLM-native navigation over structured markdown up to 400K words.
motion
How an agent turns a character mesh into a usable animated FBX — and how to judge whether the result is shippable.
stss
Reduce defensive disclaimers, stacked hedging, and self-protective narration in proposals and decision-facing writing. Use when the user asks to rewrite or audit a proposal, plan, research contribution, executive summary, or similar text for directness. Do not use for ordinary code work or unrelated prose.