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 build-and-runtime-verificationgit 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/build-and-runtime-verification)<a href="https://agentmods.dev/skills/hoatv2211/gamestudio-codexkit/build-and-runtime-verification"><img src="https://agentmods.dev/badge/skills/hoatv2211/gamestudio-codexkit/build-and-runtime-verification.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.00041 | $0.00786 |
| Opus 5 | $0.00020 | $0.00393 |
| Sonnet 5 | $0.00008 | $0.00157 |
| Haiku 4.5 | $0.00004 | $0.00079 |
Grade A, and why
build-and-runtime-verification 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.
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.
Build and Runtime Verification
Overview
Verification is a reproducible claim: exact command, environment, exit code, observable artifact, verdict, and limitations.
When to use
Use after implementation, before completion claims, for build failures, runtime smoke checks, script compilation, generated artifact comparison, or release preflight.
When NOT to use
Do not use a compile-only result to claim gameplay, performance, database, network, or regression safety that was not exercised.
Required inputs and context discovery
Collect repository root, expected command, prerequisites, environment/version snapshot, expected artifact, timeout, safe side effects, and what the check does not prove.
Safety and risk level
The gate is read-only with respect to source. If a command starts services, writes caches, imports data, opens an editor, or mutates external state, route through the relevant safety workflow first.
Workflow
- Define the claim and the single command or command sequence that proves it. Completion criterion: success and failure signals are explicit before execution.
- Verify prerequisites and capture environment versions without changing them. Completion criterion: missing dependencies are labeled BLOCKED.
- Run the narrowest check and capture stdout, stderr, duration, and exit code. Completion criterion: raw results are available even when the command fails.
- Inspect the expected artifact or runtime signal rather than relying on exit code alone. Completion criterion: artifact existence and relevant properties are recorded.
- Issue PASS, FAIL, or BLOCKED with limitations. Completion criterion: the verdict does not exceed what the evidence proves.
Evidence and output contract
Produce verdict.md or a summary JSON with claim, command, exit code, artifact path, environment snapshot, verdict, limitations, and reviewer when required.
Handoff contract
Include failing command, first actionable error, artifact/log paths, prerequisites, retries already attempted, and the safest next diagnostic step.
What ships with it
2 files 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 · 79 lines · 41 tokens per session scan A d8ec67c023e6
build-and-runtime-verification is a skill published in the GitHub repository hoatv2211/GameStudio-CodexKIT (3 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 786 once invoked, about $0.0002 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
vibe-adversarial-test-generation
Generates edge case, failure mode, and spec-driven test cases. Covers boundary values, nil inputs, concurrency, resource exhaustion, malformed data, and requirement-linked traceability tests.
vibe-coverage-enforcer
Enforces tiered test coverage standards with three dimensions — line coverage by tier, spec-to-test traceability, and spec-to-code implementation mapping. Use before claiming code is complete.
vibe-fuzz-parser-inputs
Generates fuzz test scaffolding for parsers handling external input (YAML, JSON, config files, user input). Seeds corpus from existing fixtures and runs initial pass.
vibe-concurrent-test-safety
Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering. Use when writing tests that involve goroutines, async operations, or shared mutable state.
vibe-golden-file-testing
Implements snapshot/golden file tests with temporal normalization so tests don't break daily. Use when implementing tests that compare output against expected snapshots.
vibe-quality-loop
Enforces the Implement→Review→Test→Fix→Loop cycle until work is clean. Use after any non-trivial implementation to prevent "good enough" exits.