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 commands/xeldaralz/everything-claude-unity/unity-skillifygit 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-skillify)<a href="https://agentmods.dev/commands/xeldaralz/everything-claude-unity/unity-skillify"><img src="https://agentmods.dev/badge/commands/xeldaralz/everything-claude-unity/unity-skillify.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.00028 | $0.00609 |
| Opus 5 | $0.00014 | $0.00304 |
| Sonnet 5 | $0.00006 | $0.00122 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
unity-skillify 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 3d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/unity-skillify — Generate Skills from Learnings
Generate a new skill from accumulated session data: $ARGUMENTS
Parse $ARGUMENTS:
- If it starts with
--install, the generated skill will be auto-placed in the correct directory - The remaining text is the topic to generate a skill for
Workflow
Step 1: Load Learnings
Read .claude/state/learnings.jsonl (or .claude/learnings.jsonl as fallback for pre-v1.3.0 projects).
If the file doesn't exist or is empty, report that no learnings are available and suggest running sessions with UNITY_HOOK_PROFILE=strict to start collecting data.
Step 2: Filter by Topic
Filter learning entries where:
- The
categoryfield matches the topic - File paths in
patternsrelate to the topic - The
branchname contains the topic keyword - Tool usage patterns suggest the topic area
Step 3: Cross-Reference Existing Skills
Read all existing skills in .claude/skills/ to avoid generating a duplicate. If a skill already covers this topic, report it and suggest updating the existing skill instead.
Step 4: Synthesize Skill
Generate a complete SKILL.md with:
---
name: [topic-kebab-case]
description: "[synthesized from learning patterns]"
globs: ["[derived from file patterns in learnings]"]
---
Content sections:
- Overview — what this skill covers (derived from learning patterns)
- Patterns — code patterns observed across sessions (with C# examples)
- Common Mistakes — issues that triggered hook warnings (from warnings data)
- Best Practices — patterns that appeared in successful sessions
Step 5: Output
If --install flag:
- Determine category (core/gameplay/systems/platform/genre/third-party) based on topic
- Create directory
.claude/skills/[category]/[name]/ - Write SKILL.md there
- Report: "Skill installed at .claude/skills/[category]/[name]/SKILL.md"
If no --install flag:
- Output the complete SKILL.md content
- Report: "Draft skill generated. To install, run: /unity-skillify --install [topic]"
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.
- 3d ago First seen · 73 lines · 28 tokens per session scan A 2e68f812411f
unity-skillify is a command published in the GitHub repository XeldarAlz/everything-claude-unity (21 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 609 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-08-30.
Other commands, from other repositories
become
Agent crystallization command. Studies a tool, role, or person and produces a portable 9-section agent that inhabits the domain - with beliefs, scar tissue, and instincts.
notebook
Low-ceremony capture for ideas (half-formed, want to mature into stories), todos (concrete actions), and notes (durable project/team facts for future recall). One-line capture, conditional elaboration AUQ. Use BEFORE thoughts get forced into stories.
cycle-design
Design a cycle — create new cycles with planned stories, detail existing planning cycles, or quick-sketch a roadmap. Detects planning docs in .craft/planning/ and sources the cycle from them when relevant.
docs
Generate or update project documentation using the crystallized doc-writer agent. Two-pass: brief (analysis + plan) then generate (write docs). Detects first-run vs update automatically.
reflect
Apply captured learnings to improve the Craft harness and project patterns. Converts .learnings.yaml into permanent updates.
research-verify
Verify existing research findings against independent primary sources. Upgrades confidence from 'sources agree' to 'independently verified.'.