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 jahro-console/unity-agent-skills --skill jahro-troubleshootinggit clone --depth 1 https://github.com/jahro-console/unity-agent-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/jahro-console/unity-agent-skills/jahro-troubleshooting)<a href="https://agentmods.dev/skills/jahro-console/unity-agent-skills/jahro-troubleshooting"><img src="https://agentmods.dev/badge/skills/jahro-console/unity-agent-skills/jahro-troubleshooting/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/jahro-console/unity-agent-skills/jahro-troubleshooting"><img src="https://agentmods.dev/badge/skills/jahro-console/unity-agent-skills/jahro-troubleshooting.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.00065 | $0.02357 |
| Opus 5 | $0.00032 | $0.01179 |
| Sonnet 5 | $0.00013 | $0.00471 |
| Haiku 4.5 | $0.00006 | $0.00236 |
Grade A, and why
jahro-troubleshooting 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 11d 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:
- jahro-troubleshooting — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jahro Troubleshooting
Diagnose and fix common Jahro issues. Follow the decision tree for the reported symptom.
Diagnostic Approach
- Identify the symptom — match to a decision tree below
- Walk the tree — check conditions in priority order
- Apply fix — provide code snippet or configuration change
- VERIFY — "Enter Play Mode, reproduce the original issue"
- If still broken — continue down the tree or escalate
Issue: Commands Not Appearing
The user added [JahroCommand] attributes but commands don't show in the console.
Decision Tree
Commands not appearing
├── Is the method static or instance?
│ ├── Instance → Is RegisterObject called?
│ │ ├── No → FIX: Add OnEnable/OnDisable registration
│ │ └── Yes → Is the object active in scene?
│ │ ├── No → Object never enables → RegisterObject never runs
│ │ └── Yes → Continue below
│ └── Static → Continue below
├── Is the correct assembly selected?
│ └── Check Tools → Jahro Settings → Assemblies Selection
│ └── Is the assembly containing this class checked?
│ ├── No → FIX: Select the assembly
│ └── Yes → Continue below
├── Is Jahro enabled?
│ ├── Check Jahro.Enabled at runtime (log it)
│ ├── Check JAHRO_DISABLE in Scripting Define Symbols
│ └── Check Auto-disable + build type
├── Is the method public?
│ └── Private/internal methods → FIX: Make public
├── Are parameter types supported?
│ └── Only: int, float, bool, string, Vector2, Vector3, enum
│ └── Custom class params → FIX: Change to supported type
└── Assembly scanning order issue?
└── Static commands discovered at startup; if class loaded late,
try manual RegisterObject or dynamic registration
Fix: Missing RegisterObject
// Add to the class with instance [JahroCommand] methods:
void OnEnable() => Jahro.RegisterObject(this);
void OnDisable() => Jahro.UnregisterObject(this);
Fix: Wrong assembly selected
- Open Tools → Jahro Settings → General Settings
- Under Assemblies Selection, check the assembly containing your class
- Your main game assembly is typically
Assembly-CSharp
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.
- 11d ago First seen · 282 lines · 65 tokens per session scan A be4b11628672
jahro-troubleshooting is a skill published in the GitHub repository jahro-console/unity-agent-skills (16 stars, last pushed 5mo ago), licensed MIT. It adds 65 tokens to every session and 2,357 once invoked, about $0.0003 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
ui-click-debug
A Unity troubleshooting skill for UI elements that do not respond to clicks. It uses a runtime raycast, a test that shows which object receives a pointer event, to find obstructions or interaction settings.
error-diagnosis
A Unity troubleshooting skill for errors shown in the Unity Console, the editor window that displays messages and failures. It reads the error and nearby logs, then checks related code to identify the cause.
console-get-logs
Retrieve Unity Editor logs from the MCP plugin's LogCollector, optionally filtered by log type or time window. Useful for debugging and monitoring Editor activity.
editor-application-get-state
Return the current state of UnityEditor.EditorApplication — playmode, paused state, compilation state, and related flags.
console-clear-logs
Clear the MCP log cache (used by 'console-get-logs') and the Unity Editor Console window. Useful for isolating logs to a specific action by clearing the slate first.
profiler-start
Enable Unity's runtime profiler and open the Profiler window. Idempotent: calling when already enabled returns the current enabled state without error.