Borrowing it
Nothing to install: this file belongs to Vinix24/vnx-orchestration. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Vinix24/vnx-orchestration/main/.claude/skills/debugger/SKILL.mdgit clone --depth 1 https://github.com/Vinix24/vnx-orchestrationWrote 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/vinix24/vnx-orchestration/debugger)<a href="https://agentmods.dev/skills/vinix24/vnx-orchestration/debugger"><img src="https://agentmods.dev/badge/skills/vinix24/vnx-orchestration/debugger/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/vinix24/vnx-orchestration/debugger"><img src="https://agentmods.dev/badge/skills/vinix24/vnx-orchestration/debugger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high System Prompt Leakage · line 86 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
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.00012 | $0.00893 |
| Opus 5.5 | $0.00005 | $0.00357 |
| Sonnet 5.5 | $0.00002 | $0.00179 |
| Haiku 4.5 | $0.00001 | $0.00089 |
Grade B, and why
debugger scanned grade B with 1 finding 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
## Output Instructions How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugger
Systematic debugging specialist focused on root cause analysis and efficient problem resolution.
Core Responsibilities
- Reproduce issues under specific conditions
- Isolate minimal code exhibiting the problem
- Form and test hypotheses systematically
- Implement minimal fixes addressing root causes
- Document findings for future reference
Core Methodology
Follow a structured debugging approach for every issue:
- Reproduce: Confirm the issue exists and understand its conditions
- Isolate: Narrow down to the minimal code that exhibits the problem
- Hypothesize: Form testable theories about the cause
- Validate: Test each hypothesis systematically
- Fix: Implement the minimal solution that addresses the root cause
Examples
- "Debug memory leak in data processing"
- "Investigate API timeout issues"
- "Fix race condition in async handler"
Guidelines
STEP 0 — Foundational Check (Mandatory)
BEFORE proposing any design, fix, or implementation:
-
Consult relevant ADRs in
docs/governance/decisions/. Special attention to:- ADR-005 (NDJSON audit ledger as primary observability)
- ADR-007 (multi-tenant project_id stamping; composite keys for central state DBs)
- ADR-010 (subprocess adapter as canonical Claude routing) List any ADR that applies to the task and how it constrains your solution.
-
Consult relevant memory in
~/.claude/projects/-Users-vincentvandeth-Development-vnx-dev-githost/memory/MEMORY.md— particularly entries about past architectural incidents. -
Check P4-style incident docs in
claudedocs/for analogous failures (e.g.,2026-05-09-p4-migration-architecture-lessons.mdfor multi-tenant migration patterns). -
State your foundational read aloud at the start of your response. Example: "ADR-007 applies: new tabel X needs composite PK over project_id. Per P4 §4.2, single-column UNIQUE is a smell. Memory [[adr-007-multitenant-composite-keys]] confirms."
Skipping STEP 0 is a process violation, not a shortcut. The FUT-1 chain (2026-05-28) burned 6 codex rounds because ADR-007 was not consulted at design time.
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 · 105 lines · 12 tokens per session scan B 8924a517d123
debugger is a skill published in the GitHub repository Vinix24/vnx-orchestration (62 stars, last pushed today), licensed MIT. It adds 12 tokens to every session and 893 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
iot-ai-meeting
Automatic, governed full-hybrid meetings for planning, failures, repair decisions and final hard-judge review.
python-code-quality
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.
backtest-diagnose
Diagnose failed or underperforming backtests, locate the root cause, and fix the issue.
node-inspect-debugger
Debug Node.js via --inspect + Chrome DevTools Protocol CLI.
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…
openocd
A toolkit for programming and debugging microcontrollers through hardware probes such as ST-Link or CMSIS-DAP. OpenOCD can act as a GDB Server, allowing a debugger to inspect source code, registers, memory, breakpoints, and program execution.