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 learnergit 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/learner)<a href="https://agentmods.dev/skills/xeldaralz/everything-claude-unity/learner"><img src="https://agentmods.dev/badge/skills/xeldaralz/everything-claude-unity/learner/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/xeldaralz/everything-claude-unity/learner"><img src="https://agentmods.dev/badge/skills/xeldaralz/everything-claude-unity/learner.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.00034 | $0.01227 |
| Opus 5.5 | $0.00014 | $0.00491 |
| Sonnet 5.5 | $0.00007 | $0.00245 |
| Haiku 4.5 | $0.00003 | $0.00123 |
Grade A, and why
learner 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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Learner — Knowledge Extraction
After resolving a non-trivial bug or discovering surprising behavior, use this skill to extract and preserve the learning. Not every fix is worth saving — apply the quality gates strictly.
When to Invoke
Consider extraction when:
- A debugging session took more than 3 back-and-forth exchanges
- The root cause was surprising or counterintuitive
- The fix required understanding a project-specific convention or quirk
- You discovered an undocumented interaction between systems
Quality Gates
ALL three gates must pass. If any fails, do not save the learning.
Gate 1: Not Googleable
Could someone find this answer with a 5-minute web search?
- Fails: "Use CompareTag instead of == for tag comparison" (standard Unity knowledge)
- Fails: "Cache GetComponent in Awake for performance" (well-documented best practice)
- Passes: "Our EventChannel ScriptableObjects must be in a Resources/ folder or they get stripped in IL2CPP builds because nothing in code holds a direct reference"
- Passes: "The CombatSystem processes damage in LateUpdate, not Update, so any health modification in Update will be overwritten"
Gate 2: Codebase-Specific
Is this specific to THIS project's architecture, conventions, or quirks?
- Fails: "UniTask is better than coroutines" (generic advice)
- Fails: "VContainer uses constructor injection" (library documentation)
- Passes: "The InventorySystem expects item IDs to be registered in ItemRegistry before any InventoryModel is created — initialization order matters"
- Passes: "Scene transitions must go through SceneSystem.LoadAsync, not SceneManager directly, because SceneSystem handles LifetimeScope cleanup"
Gate 3: Required Real Effort
Did this take actual debugging effort to discover?
- Fails: Missing semicolon, typo in field name, wrong import
- Fails: Obvious null reference from unassigned SerializeField
- Passes: Subtle race condition between async scene load and VContainer injection
- Passes: Serialization depth limit causing data truncation in nested inventory structure
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 · 106 lines · 34 tokens per session scan A e06d3789b97d
learner is a skill published in the GitHub repository XeldarAlz/everything-claude-unity (24 stars, last pushed 5mo ago), licensed MIT. It adds 34 tokens to every session and 1,227 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-08-30.
Other skills, from other repositories
context-management
Strategies for managing AI agent context windows including optimization, summarization, retrieval-augmented generation, progressive disclosure, and pruning. Use when the user is hitting context limits, building long-running agents, implementing RAG, optimizing token usage, or designing systems that need to manage…
error-tracing
Read stack traces, follow error chains, and trace errors to their root cause. Use when the user encounters an error message, stack trace, exception, or crash. Apply when debugging async errors, React error boundaries, source map issues, or when an error message is unclear.
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.
log-analysis
Implement structured logging and analyze logs to diagnose issues. Use when the user sets up logging, asks about log levels, needs to trace requests through distributed systems, or is analyzing log output to debug a problem. Apply when adding logging to any application.
express-error-handling
Express.js error handling patterns including async error catching, custom error classes, centralized error middleware, and the distinction between operational and programmer errors. Use when the user is handling errors in Express, writing async route handlers, creating custom error types, or debugging unhandled…
error-handling-go
Implement robust Go error handling with wrapping, sentinel errors, and custom types. Use when the user handles errors in Go, creates custom error types, wraps errors with fmt.Errorf and %w, uses errors.Is/As, or asks about Go error best practices and error propagation strategies.