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 agentmods add skills/idocohen560/claude-unity-game-studio/tools-unity-memorypacknpx skills add IdoCohen560/claude-unity-game-studio --skill tools-unity-memorypackgit 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-memorypack)<a href="https://agentmods.dev/skills/idocohen560/claude-unity-game-studio/tools-unity-memorypack"><img src="https://agentmods.dev/badge/skills/idocohen560/claude-unity-game-studio/tools-unity-memorypack.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 | $0.00026 | $0.02942 |
| Opus 5 | $0.00013 | $0.01471 |
| Sonnet 5 | $0.00005 | $0.00588 |
| Haiku 4.5 | $0.00003 | $0.00294 |
Grade A, and why
tools-unity-memorypack 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 yesterday.
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-memorypack — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 572 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MemoryPack
Overview
MemoryPack is a high-performance zero-allocation serializer for C#. This skill covers patterns for Unity serialization, custom formatters, and performance optimization.
When to Use
- Game save data
- Network message serialization
- Asset data serialization
- Cache/persistence systems
- High-frequency serialization needs
Basic Usage
Serializable Class
using MemoryPack;
[MemoryPackable]
public partial class PlayerSaveData
{
public string PlayerId;
public string PlayerName;
public int Level;
public float Experience;
public Vector3 Position;
public List<ItemData> Inventory;
public Dictionary<string, int> Statistics;
[MemoryPackConstructor]
public PlayerSaveData() { }
}
[MemoryPackable]
public partial class ItemData
{
public string ItemId;
public int Quantity;
public int Durability;
}
Serialization/Deserialization
public class SaveSystem
{
public byte[] Serialize<T>(T data)
{
return MemoryPackSerializer.Serialize(data);
}
public T Deserialize<T>(byte[] bytes)
{
return MemoryPackSerializer.Deserialize<T>(bytes);
}
public async UniTask SaveToFileAsync(string path, PlayerSaveData data)
{
byte[] bytes = MemoryPackSerializer.Serialize(data);
await File.WriteAllBytesAsync(path, bytes);
}
public async UniTask<PlayerSaveData> LoadFromFileAsync(string path)
{
if (!File.Exists(path))
return null;
byte[] bytes = await File.ReadAllBytesAsync(path);
return MemoryPackSerializer.Deserialize<PlayerSaveData>(bytes);
}
}
Unity Type Formatters
Vector3 Formatter
using MemoryPack;
using UnityEngine;
public class Vector3Formatter : MemoryPackFormatter<Vector3>
{
public override void Serialize<TBufferWriter>(
ref MemoryPackWriter<TBufferWriter> writer,
scoped ref Vector3 value)
{
writer.WriteUnmanaged(value.x);
writer.WriteUnmanaged(value.y);
writer.WriteUnmanaged(value.z);
}
public override void Deserialize(
ref MemoryPackReader reader,
scoped ref Vector3 value)
{
value.x = reader.ReadUnmanaged<float>();
value.y = reader.ReadUnmanaged<float>();
value.z = reader.ReadUnmanaged<float>();
}
}
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.
- yesterday First seen · 572 lines · 26 tokens per session scan A ce0a417fd4f1
tools-unity-memorypack is a skill published in the GitHub repository IdoCohen560/claude-unity-game-studio (17 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 2,942 once invoked, about $0.0001 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
swarm
Run a multi-agent audit of a codebase by spawning specialized parallel subagents (security, performance, tests, architecture, dead-code), then synthesize their findings into a single prioritized action plan. Use this whenever the user runs /swarm, asks to "audit the repo," "review this codebase," "find issues across…
memory-loop-setup
Bootstrap the memory loop into any repo or Obsidian vault. Triggers: (1) "set up the memory loop / second brain / warm layer here" or "install this structure in another repo/vault", (2) a new project asking "make the AI remember across sessions and surfaces".
discord-intent-application
Helps write the justification text for Discord Developer Portal privileged intent applications (Message Content, Server Members, Presence) for a specific bot. Takes a plain-text description of the bot's functionality and/or an uploaded/local codebase, screens the bot's features against Discord's known rejection…
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…
generate-tasks
Phase 3 of 5 — slices the ARCH doc into verification-ready task specs (tdd/test-after/ui/checklist), emitted as a separate TASKS- - .md file alongside ARCH for the implement skill. Use only when the user asks to run Phase 3 or generate tasks from an ARCH doc — never trigger automatically.