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 striderZA/OpenCodeGameStudios --skill automated-smoke-testgit clone --depth 1 https://github.com/striderZA/OpenCodeGameStudiosWrote 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/striderza/opencodegamestudios/automated-smoke-test)<a href="https://agentmods.dev/skills/striderza/opencodegamestudios/automated-smoke-test"><img src="https://agentmods.dev/badge/skills/striderza/opencodegamestudios/automated-smoke-test/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/striderza/opencodegamestudios/automated-smoke-test"><img src="https://agentmods.dev/badge/skills/striderza/opencodegamestudios/automated-smoke-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 155 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
- high Anti-Refusal · line 170 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
- medium MCP Rug Pull · line 26 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00035 | $0.01608 |
| Opus 5.5 | $0.00014 | $0.00643 |
| Sonnet 5.5 | $0.00007 | $0.00322 |
| Haiku 4.5 | $0.00003 | $0.00161 |
Grade A, and why
automated-smoke-test 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 1mo 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automated Smoke Test
This skill runs a fully automated smoke test against the Godot project using the godot-mcp server. It launches the project headlessly, captures debug output for a configurable duration, and analyzes the output for errors, warnings, and assertions — producing a structured pass/fail report.
No manual verification required. The entire check is automated through MCP.
Phase 1: Verify godot-mcp Availability
Call get_godot_version via the godot-mcp server. If the call succeeds, note
the version string. If it fails, inform the user:
"godot-mcp server is not available. Install it with:
npx @coding-solo/godot-mcpThen configure the MCP server inopencode.json."
Stop if the server is unavailable.
Phase 2: Read Project Info
Call get_project_info via godot-mcp. Record:
- Project title — from the project info response
- Main scene — the configured main scene path
- Render mode — e.g. Forward+, Mobile, GL Compatible
If get_project_info fails, retry up to 3 times with a 2-second delay between
attempts. If all retries fail: "Could not read project info after 3 attempts. Is
the godot-mcp server running against the correct project?" Then stop.
Phase 3: Run the Project
Parse the optional argument for duration. If no argument is provided, default
to 10 seconds. The argument is in seconds: /automated-smoke-test 15 means
capture output for 15 seconds.
Call run_project via godot-mcp. The project must respond (start or error)
within 30 seconds. If no response within the timeout, treat as a failure:
- Report: "Project failed to respond within 30 seconds — the project may be hung or the engine may have frozen during launch."
- Verdict: FAIL
- Skip to Phase 7 (Report) — the project is unresponsive, stop would also hang
If run_project returns an error or the project fails to start:
- Report: "Project failed to start with error: [error message]"
- Verdict: FAIL
- Skip to Phase 7 (Report) — project was never launched, no stop needed
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.
- 1mo ago First seen · 198 lines · 35 tokens per session scan A d38f581967a8
automated-smoke-test is a skill published in the GitHub repository striderZA/OpenCodeGameStudios (99 stars, last pushed 13d ago), licensed MIT. It adds 35 tokens to every session and 1,608 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-09-03.
Other skills, from other repositories
team-combat
Orchestrate the combat team: coordinates game-designer, gameplay-programmer, ai-programmer, technical-artist, sound-designer, and qa-tester to design, implement, and validate a combat feature end-to-end.
team-polish
Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.
procgen-design
Design procedural content systems with seeds, constraints, and validation gates so generated output stays fun and shippable.
animation-state-patterns
Structure animation state, blending, events, and sync so authored motion remains reliable under gameplay pressure.
qa-test-matrix
Build a coverage matrix that shows what must be tested, on which configurations, and at what milestone confidence level.
godot-testing
Choose effective automated and manual test layers for Godot features without overcomplicating the project.