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 skills/ouzlifaneyassine1-dot/onyx-engine/debugnpx skills add ouzlifaneyassine1-dot/onyx-engine --skill debuggit clone --depth 1 https://github.com/ouzlifaneyassine1-dot/onyx-engineWrote 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/ouzlifaneyassine1-dot/onyx-engine/debug)<a href="https://agentmods.dev/skills/ouzlifaneyassine1-dot/onyx-engine/debug"><img src="https://agentmods.dev/badge/skills/ouzlifaneyassine1-dot/onyx-engine/debug.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.00077 | $0.02931 |
| Opus 5 | $0.00039 | $0.01465 |
| Sonnet 5 | $0.00015 | $0.00586 |
| Haiku 4.5 | $0.00008 | $0.00293 |
Grade A, and why
debug 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 5d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/debug — Triage and Fix a Bug End-to-End
The disciplined debugging loop for Godot/onyx projects. Read the error before guessing. Form a hypothesis before editing. Verify the fix before declaring victory. Never grep the codebase before reading the actual error.
Core principle: The debugger already knows what's wrong. Your job is to listen to it before doing anything else.
When to use this skill
- The user says "it crashes", "it broke", "throws an error", "doesn't work", "freezes", "wrong behavior".
- The user pastes a stack trace.
- A previous build or test step failed and the user wants to fix it.
When NOT to use this skill
- The user is asking how to prevent a class of bug — that's a design question. Use the relevant discipline skill (
gdscript-patterns,scene-composition). - The user is asking for a feature with a known unfinished spec — that's
make-gameterritory. - The bug is in a non-Godot file the host agent can debug natively (CI config, npm scripts) — use the host's debugger.
The Loop
Listen → Diagnose → Hypothesize → Propose → Fix → Verify
Do not skip steps. Do not loop back to "Hypothesize" without re-running the cheap diagnostic.
1. Listen
Ask the user one focused question and wait for the answer:
What's happening, and when does it happen?
If they already gave a clear symptom in the request, skip the question. If they say "something's broken", that one question is your only call until they reply. Don't run tools yet.
2. Diagnose — cheapest tool first
In strict order. Stop at the first one that returns useful signal.
| Order | Tool | When |
|---|---|---|
| 1 | onyx_get_script_errors |
Always start here. Catches GDScript parse errors, missing identifiers, signature mismatches. Cheapest, no side effects. |
| 2 | onyx_get_diagnostics |
Aggregate console + debugger error counts. One call, broad picture. |
| 3 | onyx_get_console |
Read the editor Output panel — print statements, warnings, errors that didn't crash. |
| 4 | onyx_get_debugger_errors |
Runtime errors caught by the debugger. Use AFTER onyx_play for runtime-only bugs. |
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.
- 5d ago First seen · 196 lines · 77 tokens per session scan A f9a9e8523a84
debug is a skill published in the GitHub repository ouzlifaneyassine1-dot/onyx-engine (0 stars, last pushed 2mo ago), licensed MIT. It adds 77 tokens to every session and 2,931 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-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…