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 MRCalderon3D/everything-game-dev-code --skill console-certificationgit clone --depth 1 https://github.com/MRCalderon3D/everything-game-dev-codeWrote 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/mrcalderon3d/everything-game-dev-code/console-certification)<a href="https://agentmods.dev/skills/mrcalderon3d/everything-game-dev-code/console-certification"><img src="https://agentmods.dev/badge/skills/mrcalderon3d/everything-game-dev-code/console-certification/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/mrcalderon3d/everything-game-dev-code/console-certification"><img src="https://agentmods.dev/badge/skills/mrcalderon3d/everything-game-dev-code/console-certification.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.00026 | $0.00341 |
| Opus 5.5 | $0.00010 | $0.00136 |
| Sonnet 5.5 | $0.00005 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
console-certification 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 22d 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.
What it actually says
Console Certification
Purpose
Prepare the project for console platform requirements, TRCs/TCRs/XRs, and first-party submission expectations.
Use When
- shipping to consoles
- platform-specific UX and entitlement flows are being added
- submission planning is underway
Inputs
- platform requirements
- current build behavior
- entitlement flow
- save and online behavior
Process
- map product behavior to platform requirement categories
- identify compliance-sensitive areas such as suspend/resume, user accounts, storage, network, and commerce
- plan targeted compliance testing
- document known waivers or uncertainty
- coordinate fixes with release planning
Outputs
- certification checklist
- platform risk list
- compliance test plan
- submission blockers
Quality Bar
- turns risk into explicit evidence and ownership
- keeps release blockers visible instead of implicit
- connects quality decisions to milestone and platform impact
Common Failure Modes
- severity inflation or minimization without player-impact context
- treating waived risks as invisible
- submission checklists that are incomplete or stale
Related Agents
- console-compliance-reviewer
- qa-lead
- release-manager
Related Commands
- cert-check
- release-check
- verify
Notes
- Keep this skill aligned with the relevant rules layer and current project documentation.
- If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.
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.
- 22d ago First seen · 60 lines · 26 tokens per session scan A 12bf5d1657a2
console-certification is a skill published in the GitHub repository MRCalderon3D/everything-game-dev-code (101 stars, last pushed 23d ago), licensed MIT. It adds 26 tokens to every session and 341 once invoked, about $0.0001 per session on Opus 5.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-10-10.
Other skills, from other repositories
asset-audit
Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard violations.
balance-check
Analyzes game balance data files, formulas, and configuration to identify outliers, broken progressions, degenerate strategies, and economy imbalances. Use after modifying any balance-related data or design. Use when user says 'balance report', 'check game balance', 'run a balance check'.
code-review
Performs an architectural and quality code review on a specified file or set of files. Checks for coding standard compliance, architectural pattern adherence, SOLID principles, testability, and performance concerns.
godot-build-optimization
Analyze a Godot project and generate a version-aware SCons export-template profile, optional .gdbuild feature profile, and reproducible artifact-size report. Use when reducing packaged engine size before export; keep runtime validation and risky binary post-processing explicit.
cgs-adopt
Use for adopt tasks that inventory existing source, assets, docs, and tests before mapping work into CGS structure; produce verification evidence, changed or proposed files, and handoff boundaries.
cgs-architecture-review
Use for architecture review tasks that review architecture for layer violations, scalability risks, engine misuse, testing seams, and production readiness; produce verification evidence, changed or proposed files, and handoff boundaries.