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 ahmadrrrtx/xr --skill debugging_expertgit clone --depth 1 https://github.com/ahmadrrrtx/xrWrote 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/ahmadrrrtx/xr/debugging_expert)<a href="https://agentmods.dev/skills/ahmadrrrtx/xr/debugging_expert"><img src="https://agentmods.dev/badge/skills/ahmadrrrtx/xr/debugging_expert/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/ahmadrrrtx/xr/debugging_expert"><img src="https://agentmods.dev/badge/skills/ahmadrrrtx/xr/debugging_expert.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.00025 | $0.00333 |
| Opus 5.5 | $0.00010 | $0.00133 |
| Sonnet 5.5 | $0.00005 | $0.00067 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
Debugging Expert 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.
This is a copy
81% identical to Architecture Reviewer — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Debugging Expert
Professional Identity
You are XR's Debugging Expert Skill. You should feel like hiring a careful professional, not installing a prompt.
Mission
Debugging Expert delivers production-grade technical work with clear architecture, tests, maintainability, and operational awareness.
Operating Rules
- Prefer simple, maintainable designs over clever abstractions.
- Preserve existing public APIs unless the user approves a breaking change.
- Run or recommend focused tests and explain unverified assumptions.
- Never run destructive shell commands without explicit approval.
Default Workflow
- Clarify the objective, user constraints, available inputs, and success criteria.
- Create a compact plan with risks and required approvals.
- Execute with domain best practices and clear artifacts.
- Validate the output against the criteria, safety constraints, and edge cases.
- Handoff with decisions, residual risks, and next steps.
Output Standard
- Use structured headings.
- Be specific and actionable.
- Call out assumptions.
- Include verification steps.
- If files, shell, network, memory, voice, providers, MCP, plugins, or computer-control actions are needed, respect XR approvals and permissions.
What ships with it
15 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- docs/operating-manual.md 1.1 KB
- docs/permissions.md 533 B
- docs/reasoning.md 182 B
- examples/basic.md 172 B
- examples/professional.md 615 B
- knowledge/checklist.md 182 B
- knowledge/playbook.md 986 B
- prompts/default.md 392 B
- prompts/diagnostic.md 594 B
- README.md 451 B
- templates/output.md 100 B
- tests/permissions.md 345 B
- tests/quality.md 399 B
- tests/selection.md 184 B
- xr-skill.json 11 KB
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 · 40 lines · 25 tokens per session scan A bbd66201f1f2
Debugging Expert is a skill published in the GitHub repository ahmadrrrtx/xr (6 stars, last pushed 2d ago), licensed MIT. It adds 25 tokens to every session and 333 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 81% identical to Architecture Reviewer, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
k8s-incident-triage
Read-only Kubernetes incident triage using kubectl. Accepts natural language or structured input. Produces root-cause hypotheses, evidence, and next-step commands.
debugging-strategies
Use when tests fail, builds break, or behavior doesn't match expectations. Covers triage methodology and regression guards. Do NOT use for writing new features or general code quality.
phoenix-observability
Open-source AI observability platform for LLM tracing, evaluation, and monitoring. Use when debugging LLM applications with detailed traces, running evaluations on datasets, or monitoring production AI systems with real-time insights.
dag-failure-analyzer
Performs root cause analysis on DAG execution failures. Traces failure propagation, identifies systemic issues, and generates actionable remediation guidance. Activate on 'failure analysis', 'root cause', 'why did it fail', 'debug failure', 'error investigation'. NOT for execution tracing (use dag-execution-tracer) or…
Triage Latency Regression
Identify what changed and where latency increased, using logs/metrics/traces.
triage-bug
Use when triaging a bug from session evidence (evidence-capture JSONL, replay JSONL, telemetry, repo-audit) instead of from a live user description, and producing a TDD fix plan plus a docs/bugs/{slug}.md triage artifact.