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 tools-unity-test-frameworkgit 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/tools-unity-test-framework)<a href="https://agentmods.dev/skills/idocohen560/claude-unity-game-studio/tools-unity-test-framework"><img src="https://agentmods.dev/badge/skills/idocohen560/claude-unity-game-studio/tools-unity-test-framework/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/tools-unity-test-framework"><img src="https://agentmods.dev/badge/skills/idocohen560/claude-unity-game-studio/tools-unity-test-framework.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.00027 | $0.03502 |
| Opus 5.5 | $0.00011 | $0.01401 |
| Sonnet 5.5 | $0.00005 | $0.00700 |
| Haiku 4.5 | $0.00003 | $0.00350 |
Grade A, and why
tools-unity-test-framework 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- tools-unity-test-framework — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 684 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unity Test Framework
Overview
Unity Test Framework provides NUnit-based testing for Unity with EditMode (fast, no runtime) and PlayMode (full Unity lifecycle) test support.
When to Use
- Unit testing game logic
- Integration testing systems
- Testing MonoBehaviour lifecycle
- Automated regression testing
- CI/CD test gates
Test Assembly Setup
Assembly Definition (EditMode)
// Tests/Editor/MyGame.Tests.Editor.asmdef
{
"name": "MyGame.Tests.Editor",
"rootNamespace": "MyGame.Tests",
"references": [
"MyGame.Core",
"MyGame.Gameplay",
"VContainer",
"UniTask"
],
"includePlatforms": [
"Editor"
],
"excludePlatforms": [],
"allowUnsafeCode": false,
"overrideReferences": true,
"precompiledReferences": [
"nunit.framework.dll",
"NSubstitute.dll"
],
"autoReferenced": false,
"defineConstraints": [
"UNITY_INCLUDE_TESTS"
],
"versionDefines": [],
"noEngineReferences": false
}
Assembly Definition (PlayMode)
// Tests/Runtime/MyGame.Tests.Runtime.asmdef
{
"name": "MyGame.Tests.Runtime",
"references": [
"MyGame.Core",
"MyGame.Gameplay",
"VContainer",
"UniTask"
],
"includePlatforms": [],
"excludePlatforms": [],
"overrideReferences": true,
"precompiledReferences": [
"nunit.framework.dll",
"NSubstitute.dll"
],
"defineConstraints": [
"UNITY_INCLUDE_TESTS"
]
}
EditMode Tests
Basic Test Structure
using NUnit.Framework;
namespace MyGame.Tests
{
[TestFixture]
public class DamageCalculatorTests
{
private DamageCalculator _calculator;
[SetUp]
public void SetUp()
{
_calculator = new DamageCalculator();
}
[TearDown]
public void TearDown()
{
_calculator = null;
}
[Test]
public void CalculateDamage_WithCrit_DoublesBaseDamage()
{
// Arrange
var baseDamage = 100;
var isCrit = true;
// Act
var result = _calculator.Calculate(baseDamage, isCrit);
// Assert
Assert.AreEqual(200, result);
}
[Test]
public void CalculateDamage_NoCrit_ReturnsBaseDamage()
{
var result = _calculator.Calculate(100, false);
Assert.AreEqual(100, result);
}
}
}
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 · 684 lines · 27 tokens per session scan A 823510af524e
tools-unity-test-framework is a skill published in the GitHub repository IdoCohen560/claude-unity-game-studio (23 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 3,502 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
test-writer
Generates comprehensive unit and integration tests for a given file or function, auto-detecting the project test framework and matching existing test style.
mvp-readiness
Runs a structured MVP quality-gate audit covering stability, security, logging, docs, and implementation integrity. Reports pass/fail with evidence.
requirements-generator
Generates structured requirements documents with functional and non-functional requirements, Gherkin acceptance criteria, edge cases, and out-of-scope items.
abd-test
ABD Testing agent: auto-detects the test framework, writes tests matching project style, runs the suite, and records a test artifact.
plan-qa
Post-implementation QA planning — independent of /review (the developer chooses whether to run them sequentially or in parallel), only when the change has a running surface worth driving. Interviews the developer to turn the specs and the diff into an executable QA specification (specs/qa/QA- - .md) that /execute-qa…
execute-qa
Executes a QA specification (specs/qa/QA- - .md) written by /plan-qa: drives every step with the plan's drivers, verifies each Expected line mechanically ([assert]) or by evidence-backed judgment against the plan's written criterion ([judge]), pauses at named operator handoffs, and writes the results artifact…