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 IdoCohen560/claude-unity-game-studio --skill security-auditgit clone --depth 1 https://github.com/IdoCohen560/claude-unity-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/idocohen560/claude-unity-game-studio/security-audit)<a href="https://agentmods.dev/skills/idocohen560/claude-unity-game-studio/security-audit"><img src="https://agentmods.dev/badge/skills/idocohen560/claude-unity-game-studio/security-audit/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/idocohen560/claude-unity-game-studio/security-audit"><img src="https://agentmods.dev/badge/skills/idocohen560/claude-unity-game-studio/security-audit.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.00049 | $0.01968 |
| Opus 5.5 | $0.00020 | $0.00787 |
| Sonnet 5.5 | $0.00010 | $0.00394 |
| Haiku 4.5 | $0.00005 | $0.00197 |
Grade A, and why
security-audit 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.
This is a copy
97% identical to security-audit — 245 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Audit
Security is not optional for any shipped game. Even single-player games have save tampering vectors. Multiplayer games have cheat surfaces, data exposure risks, and denial-of-service potential. This skill systematically audits the codebase for the most common game security failures and produces a prioritised remediation plan.
Run this skill:
- Before any public release (required for the Polish → Release gate)
- Before enabling any online/multiplayer feature
- After implementing any system that reads from disk or network
- When a security-related bug is reported
Output: production/security/security-audit-[date].md
Phase 1: Parse Arguments and Scope
Modes:
full— all categories (recommended before release)network— network/multiplayer onlysave— save file and serialization onlyinput— input validation and injection onlyquick— high-severity checks only (fastest, for iterative use)- No argument — run
full
Read .claude/docs/technical-preferences.md to determine:
- Engine and language (affects which patterns to search for)
- Target platforms (affects which attack surfaces apply)
- Whether multiplayer/networking is in scope
Phase 2: Spawn Security Engineer
Spawn security-engineer via Task. Pass:
- The audit scope/mode
- Engine and language from technical preferences
- A manifest of all source directories:
src/,assets/data/, any config files
The security-engineer runs the audit across 6 categories (see Phase 3). Collect their full findings before proceeding.
Phase 3: Audit Categories
The security-engineer evaluates each of the following. Skip categories not applicable to the project scope.
Category 1: Save File and Serialization Security
- Are save files validated before loading? (no blind deserialization)
- Are save file paths constructed from user input? (path traversal risk)
- Are save files checksummed or signed? (tamper detection)
- Does the game trust numeric values from save files without bounds checking?
- Are there any eval() or dynamic code execution calls near save loading?
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 · 245 lines · 49 tokens per session scan A d46a7f943b1a
security-audit is a skill published in the GitHub repository IdoCohen560/claude-unity-game-studio (23 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 1,968 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to security-audit, differing in 245 lines, and is treated as a copy.
Other skills, from other repositories
full-security-review
Structured security audit covering injection, auth, secrets, input validation, dependencies, cryptography, and AI/LLM risks. Produces severity-graded findings.
accessibility
Audits code for WCAG 2.2 AA compliance and provides design guidance for accessible components. Covers semantic HTML, ARIA, keyboard nav, contrast, focus management, and motion.
dependency-audit
Audits project dependencies across package.json, requirements.txt, go.mod, Cargo.toml, Gemfile, composer.json, and .NET projects for unpinned versions, deprecated packages, missing lockfiles, and known CVEs.
git-workflow
Enforces the release-branch Git model: scaffold feature branches, open PRs with review checks, cut releases with tags, and view workflow reference.
log-correlation
Correlates and troubleshoots logs across OS (Linux/macOS), AWS (CloudWatch, CloudTrail, ALB, Lambda), application (JSON, logfmt), and web servers (Nginx, Apache).
api-design
Designs REST, GraphQL, and gRPC APIs (OpenAPI/schema/proto output) and reviews existing APIs for consistency, best practices, and breaking change risks.