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 XeldarAlz/everything-claude-unity --skill vcontainergit clone --depth 1 https://github.com/XeldarAlz/everything-claude-unityWrote 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/xeldaralz/everything-claude-unity/vcontainer)<a href="https://agentmods.dev/skills/xeldaralz/everything-claude-unity/vcontainer"><img src="https://agentmods.dev/badge/skills/xeldaralz/everything-claude-unity/vcontainer.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.00038 | $0.02567 |
| Opus 5 | $0.00019 | $0.01283 |
| Sonnet 5 | $0.00008 | $0.00513 |
| Haiku 4.5 | $0.00004 | $0.00257 |
Grade A, and why
vcontainer 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 4d 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 — 443 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VContainer — Dependency Injection for Unity
VContainer is a lightweight, fast DI framework for Unity by hadashiA. It provides constructor injection for plain C# classes, method injection for MonoBehaviours, hierarchical scoping, and lifecycle management without the complexity of Zenject.
Why Dependency Injection in Unity
- Decouple systems: Components depend on interfaces, not concrete types
- Testability: Swap real implementations for mocks in tests
- No singletons: Avoid static state and its hidden coupling
- Configurable composition: Change wiring without changing code
- Explicit dependencies: Constructor parameters document what a class needs
LifetimeScope Hierarchy
VContainer uses LifetimeScope MonoBehaviours as composition roots. They form a parent-child hierarchy for dependency resolution.
RootLifetimeScope (DontDestroyOnLoad)
|- AudioService (Singleton)
|- SaveSystem (Singleton)
|- AnalyticsService (Singleton)
+- ISettingsProvider (Singleton)
|
|- MainMenuLifetimeScope (MainMenu scene)
| |- MainMenuController
| +- LeaderboardService
|
+- GameLifetimeScope (Game scene)
|- GameManager
|- SpawnSystem
+- ScoreSystem
Root Scope (Project-Wide Services)
using VContainer;
using VContainer.Unity;
public class RootLifetimeScope : LifetimeScope
{
[SerializeField] private AudioSettings _audioSettings;
protected override void Configure(IContainerBuilder builder)
{
// Singletons survive scene loads
builder.Register<AudioService>(Lifetime.Singleton).As<IAudioService>();
builder.Register<SaveSystem>(Lifetime.Singleton).As<ISaveSystem>();
builder.Register<AnalyticsService>(Lifetime.Singleton).As<IAnalyticsService>();
// ScriptableObject instance
builder.RegisterInstance(_audioSettings);
}
}
Scene Scope (Scene-Specific)
public class GameLifetimeScope : LifetimeScope
{
[SerializeField] private LevelConfig _levelConfig;
protected override void Configure(IContainerBuilder builder)
{
// Scene-specific registrations
builder.Register<ScoreSystem>(Lifetime.Scoped);
builder.Register<WaveSpawner>(Lifetime.Scoped);
// Entry point with lifecycle
builder.RegisterEntryPoint<GameFlowController>();
// MonoBehaviour already in scene hierarchy
builder.RegisterComponentInHierarchy<PlayerController>();
builder.RegisterComponentInHierarchy<HUDManager>();
// Config data
builder.RegisterInstance(_levelConfig);
}
}
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.
- 4d ago First seen · 443 lines · 38 tokens per session scan A af0249e81e04
vcontainer is a skill published in the GitHub repository XeldarAlz/everything-claude-unity (22 stars, last pushed 4mo ago), licensed MIT. It adds 38 tokens to every session and 2,567 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-09-03.
Other skills, from other repositories
systematic-debugging
Apply structured debugging techniques to find and fix bugs efficiently. Use when the user reports a bug, encounters unexpected behavior, says something is "not working", or asks for help debugging. Apply hypothesis-driven debugging instead of random changes.
junit-testing
JUnit 5 testing patterns including annotations, Mockito mocking, Spring Boot test slices, MockMvc, Testcontainers integration, and parameterized tests. Use when the user is writing Java tests, setting up test infrastructure, mocking dependencies, testing Spring controllers, or running integration tests with real…
mocking-strategies
Mocks vs stubs vs spies, dependency injection for testing, jest.mock/unittest.mock/gomock, and when NOT to mock. Use when the user needs to isolate dependencies in tests, asks about mocking external services, or has tests tightly coupled to implementation details.
tdd-workflow
Red-green-refactor TDD cycle, test-first methodology, coverage targets (80%+), and test pyramid. Use when the user is implementing a new feature, fixing a bug, asks about TDD, or mentions writing tests before code. Always push for test-first.
test-architecture
Test organization, fixtures, factories (factoryboy/faker), test isolation, database cleanup, and test configuration. Use when the user is setting up a test suite, organizing test files, creating test fixtures, or dealing with test isolation issues.
automation-triggers
Patterns for auto-format on save, auto-lint, auto-test on file change, and CI triggers within Claude Code. Use when the user wants automated reactions to file changes, wants to set up continuous feedback loops, or asks about triggering actions automatically.