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.
git 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/commands/xeldaralz/everything-claude-unity/unity-instincts)<a href="https://agentmods.dev/commands/xeldaralz/everything-claude-unity/unity-instincts"><img src="https://agentmods.dev/badge/commands/xeldaralz/everything-claude-unity/unity-instincts.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.00032 | $0.01297 |
| Opus 5 | $0.00016 | $0.00648 |
| Sonnet 5 | $0.00006 | $0.00259 |
| Haiku 4.5 | $0.00003 | $0.00130 |
Grade A, and why
unity-instincts 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.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/unity-instincts — Instinct Library
Manage atomic Unity-specific learnings: $ARGUMENTS
Instincts are atomic learned behaviors captured by instinct-capture.sh (PostToolUse) and distilled by instinct-distill.sh (Stop). Each instinct has: a trigger, an action, a confidence score (0.3–0.9), an evidence count, and a scope (project or global).
Storage:
- Project instincts:
.claude/state/instincts/project/<project-hash>/*.json - Global instincts:
.claude/state/instincts/global/*.json - Raw observations:
.claude/state/instincts/observations.jsonl
Subcommands
status (default)
Show a dashboard of the instinct library for the current project.
- Compute project hash:
git config --get remote.origin.url | shasum | head -c 12(or fallback togit rev-parse --show-toplevel). - List files under
.claude/state/instincts/project/<hash>/and.claude/state/instincts/global/. - For each instinct, read JSON fields and render:
## Instinct Library
**Project:** <project-hash>
**Project instincts:** <count> (<count-above-0.7> high-confidence)
**Global instincts:** <count>
**Raw observations:** <count> (this session: <count>)
### High confidence (>= 0.7) — project
| Trigger | Action | Confidence | Evidence |
|---|---|---|---|
| before editing *View.cs | expect quality-gate warnings; read Model first | 0.8 | 12 |
| ... | ... | ... | ... |
### Medium (0.5–0.69) — project
...
### Low (0.3–0.49) — project
...
### Global (all scopes)
...
Sort within each band by evidence_count desc.
list [--domain <d>] [--min-confidence <n>]
Filter and list instincts. Useful when the library grows:
/unity-instincts list --domain mvs
/unity-instincts list --min-confidence 0.7
Read JSON files, filter, output the same table format as status but limited to the filtered set.
evolve [--min-confidence 0.8]
Graduate high-confidence instincts into draft skill files.
- Collect instincts from project and global scopes with
confidence >= N(default 0.8) ANDevidence_count >= 5. - Group by
domain. - For each domain cluster, draft a SKILL.md:
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 · 143 lines · 32 tokens per session scan A 91e5bacfa25b
unity-instincts is a command published in the GitHub repository XeldarAlz/everything-claude-unity (21 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 1,297 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-08-30.
Other commands, from other repositories
story-continue
Resume an interrupted story from where you left off.
nds-test
Read the knowledge base BEFORE any MCP tool call.
gba-ai-full
Read docs/gba-claude-guide.md from C:\Users\AustinKidwell\ASR Dropbox\Austin Kidwell\04ResearchAnalysis\pokefirered-master\pokefirered-master completely before any MCP tool call.
gba-build-develop
Composes /gba-build develop, /gba-ai-full, /research-perplexity, /creative-research, and /orchestrator-multi into a single autonomous mega-pipeline that researches, plans, parallelizes implementation, AI-playtests, iterates on failures, discovers creative features, and ships production-ready GBA games.
nds-build
Command "nds-build" from intellegix/intellegix-code-agent-toolkit, covering /nds-build — universal nds game builder, usage, subcommands, new — scaffold a new nds project and develop — research-driven modular game build.
review
Run code review on recent changes.