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 Nice-Wolf-Studio/unity-claude-skills --skill unity-npc-behaviorgit clone --depth 1 https://github.com/Nice-Wolf-Studio/unity-claude-skillsWrote 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/nice-wolf-studio/unity-claude-skills/unity-npc-behavior)<a href="https://agentmods.dev/skills/nice-wolf-studio/unity-claude-skills/unity-npc-behavior"><img src="https://agentmods.dev/badge/skills/nice-wolf-studio/unity-claude-skills/unity-npc-behavior.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.00075 | $0.09886 |
| Opus 5 | $0.00037 | $0.04943 |
| Sonnet 5 | $0.00015 | $0.01977 |
| Haiku 4.5 | $0.00007 | $0.00989 |
Grade A, and why
unity-npc-behavior 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 7d 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:
- unity-npc-behavior — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 1,272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NPC Behavior -- Design Translation Patterns
Prerequisite skills:
unity-physics-queries(perception raycasts, NonAlloc query patterns),unity-state-machines(decision FSM/BT architecture),unity-game-architecture(event bus, Service Locator, component composition)
Claude's default NPC is a single MonoBehaviour with an Update() that raycasts, decides, and moves all in one method. This is untestable and unextensible -- changing perception logic requires touching decision logic, adding a new sense means rewriting the entire method, and squad coordination is impossible when each NPC is a self-contained island. These patterns decompose NPC behavior into pluggable layers that designers can configure without programmer intervention.
PATTERN: Perception System Architecture
DESIGN INTENT: NPCs sense the world through sight, hearing, and proximity. Different NPC types have different senses -- a guard has long-range sight but poor hearing; a dog has short sight but exceptional hearing. Senses are mix-and-match components that feed a unified target list.
WRONG (Claude default):
// Raycast inside decision code -- can't swap senses, no batching, untestable
public class EnemyAI : MonoBehaviour
{
void Update()
{
// Perception and decision jammed together
var dir = (player.position - transform.position).normalized;
if (Physics.Raycast(transform.position, dir, out var hit, 20f))
{
if (hit.collider.CompareTag("Player"))
{
// Immediately decide and act -- no separation
Chase(hit.collider.transform);
}
}
}
}
RIGHT:
/// <summary>
/// Pluggable sense interface. Each sense is a separate component on the NPC.
/// Cross-ref: unity-physics-queries for OverlapSphereNonAlloc and raycast patterns.
/// </summary>
public interface IPerceptionSense
{
/// <summary>Evaluate targets within range. Called by PerceptionComponent on staggered schedule.</summary>
void EvaluateTargets(Collider[] scratchBuffer, List<PerceivedTarget> results);
/// <summary>Maximum range of this sense for broad-phase overlap sphere.</summary>
float MaxRange { get; }
}
/// <summary>
/// Central perception hub. Collects results from all IPerceptionSense components.
/// Maintains a deduplicated KnownTargets list for the decision layer.
/// </summary>
public class PerceptionComponent : MonoBehaviour
{
[SerializeField] private float _updateInterval = 0.2f;
[SerializeField] private LayerMask _detectionLayers;
private readonly List<PerceivedTarget> _knownTargets = new();
private IPerceptionSense[] _senses;
private readonly Collider[] _scratchBuffer = new Collider[32];
public IReadOnlyList<PerceivedTarget> KnownTargets => _knownTargets;
}
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 1,272 lines · 75 tokens per session scan A 01a6af737203
unity-npc-behavior is a skill published in the GitHub repository Nice-Wolf-Studio/unity-claude-skills (30 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session and 9,886 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
gameobject-component-destroy
Destroy one or more Components from a target GameObject. Missing (null) components are skipped — they cannot be destroyed. Use 'gameobject-find' and 'gameobject-component-get' to identify the components first.
unity-version-split
Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).
unity-addressables
Manage Addressables groups, entries, profiles and content builds (com.unity.addressables, reflection-based).
playtest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
unity-manual-component
Manually add, configure, reorder, and copy components on GameObjects using Unity Editor UI. For one-off Inspector workflows that do not need REST automation.
motion
How an agent turns a character mesh into a usable animated FBX — and how to judge whether the result is shippable.