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 load-soak-capacity-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/load-soak-capacity-verification)<a href="https://agentmods.dev/skills/hoatv2211/gamestudio-codexkit/load-soak-capacity-verification"><img src="https://agentmods.dev/badge/skills/hoatv2211/gamestudio-codexkit/load-soak-capacity-verification/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/load-soak-capacity-verification"><img src="https://agentmods.dev/badge/skills/hoatv2211/gamestudio-codexkit/load-soak-capacity-verification.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.00052 | $0.00848 |
| Opus 5 | $0.00026 | $0.00424 |
| Sonnet 5 | $0.00010 | $0.00170 |
| Haiku 4.5 | $0.00005 | $0.00085 |
Grade A, and why
load-soak-capacity-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 9d 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.
Load Soak Capacity Verification
Overview
Provide an evidence-first contract for load, soak, concurrency, capacity, saturation, queues, leaks, failover, recovery, scaling, baselines, and stop conditions.
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 client FPS budgets or uncontrolled production load testing.
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 medium. 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
- Define environment, topology, dataset, traffic model, baseline, SLOs, and abort thresholds. Completion criterion: evidence is recorded and unresolved items are explicit.
- Verify authorization, isolation, observability, cleanup, and recovery before generating load. Completion criterion: evidence is recorded and unresolved items are explicit.
- Run stepped load and bounded soak while capturing latency, errors, saturation, queues, and resources. Completion criterion: evidence is recorded and unresolved items are explicit.
- Test degradation, scaling, failover, recovery, and leak hypotheses against baselines. Completion criterion: evidence is recorded and unresolved items are explicit.
- Return measured capacity, confidence, bottlenecks, artifacts, and BLOCKED gaps. Completion criterion: evidence is recorded and unresolved items are explicit.
Evidence and output contract
Produce load-soak-report.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.
- 9d ago First seen · 79 lines · 52 tokens per session scan A 4e6a2e716d5b
load-soak-capacity-verification is a skill published in the GitHub repository hoatv2211/GameStudio-CodexKIT (3 stars, last pushed 2d ago), licensed MIT. It adds 52 tokens to every session and 848 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
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-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-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-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.