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 javiarmesto/ALDC-AL-Development-Collection --skill skill-debuggit clone --depth 1 https://github.com/javiarmesto/ALDC-AL-Development-CollectionWrote 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/javiarmesto/aldc-al-development-collection/skill-debug)<a href="https://agentmods.dev/skills/javiarmesto/aldc-al-development-collection/skill-debug"><img src="https://agentmods.dev/badge/skills/javiarmesto/aldc-al-development-collection/skill-debug/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/javiarmesto/aldc-al-development-collection/skill-debug"><img src="https://agentmods.dev/badge/skills/javiarmesto/aldc-al-development-collection/skill-debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00028 | $0.02239 |
| Opus 5 | $0.00014 | $0.01120 |
| Sonnet 5 | $0.00006 | $0.00448 |
| Haiku 4.5 | $0.00003 | $0.00224 |
Grade A, and why
skill-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 9d 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: AL Debugging & Diagnostics
Purpose
Systematic diagnosis and root cause analysis for AL Business Central issues: runtime errors, logic bugs, intermittent failures, performance bottlenecks, and configuration problems.
When to Load
This skill should be loaded when:
- A runtime error, exception, or unexpected behavior is reported
- A logic bug needs root cause analysis (not just a symptom fix)
- An intermittent issue needs snapshot capture
- A performance bottleneck needs CPU profiling
- Configuration issues (auth, symbols, build, publishing) block development
- An event subscriber is not firing as expected
Core Patterns
Pattern 1: Choose Debugging Strategy
Select the right tool before starting:
| Issue Type | Strategy | Tool |
|---|---|---|
| Consistent runtime error | Standard debugger | VS Code AL debugger (attach, no publish) — human step |
| Already deployed code | Debug without publish | VS Code AL debugger (attach, no publish) — human step |
| Rapid dev cycle | Incremental publish | VS Code RAD publish (AL: Publish without Debugging) — human step |
| Intermittent / hard-to-reproduce | Snapshot debugging | VS Code snapshot debugging — human step |
| Slow performance | CPU profiling | VS Code CPU profiler — human step |
| Auth / symbols / build | Configuration troubleshoot | See Workflow Step 2b |
| Copilot AI feature | Agent session debug | launch.json with clientType: Agent |
Pattern 2: Data Flow Tracing
Scenario: "Value is wrong after posting"
1. Set breakpoint at final location (where value is wrong)
2. Work backwards to find where value is set
3. Use `usages` tool to find all assignments
4. Set breakpoints at each assignment point
5. Step through to find which execution path is taken
6. Inspect conditions and variable states at each point
Pattern 3: Event Subscriber Not Firing
Scenario: "My event subscriber doesn't execute"
1. Verify subscriber signature exactly matches publisher (name, parameters, types)
2. Check SkipOnMissingLicense and SkipOnMissingPermission attributes
3. Confirm the extension containing the publisher is active and published
4. Set breakpoint inside subscriber body
5. Verify the publisher event is actually being raised (breakpoint in publisher)
6. Check if IsHandled = true is set before your subscriber runs
7. Inspect subscriber execution order (EventPriority)
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.
- 9d ago First seen · 251 lines · 28 tokens per session scan A 1cb52bafa2fa
skill-debug is a skill published in the GitHub repository javiarmesto/ALDC-AL-Development-Collection (103 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 2,239 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 skills, from other repositories
debugging-and-error-recovery
Use when encountering unexpected behavior, crashes, or test failures in Android. Six-step triage from reproduction to regression guard, using Logcat, Android Studio debugger, and profiling tools.
refactor
Surgical code refactoring to improve maintainability without changing behaviour. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.
langsmith-tracing
LangSmith tracing and debugging setup for LLM applications. Configure observability, capture traces, and enable debugging for LangChain/LangGraph agents.
hotfix-triage
Urgent issue classification, root cause analysis, and fast-path routing for production hotfixes.
spk-admin-setup-doctor
Install, verify, and repair Spec Kitty commands, skills, agent paths, runtime prerequisites, and common setup failures.
debug
Run /debug to find and fix a bug's root cause: a test failing for an unclear reason, /check verify finding a failure, or behavior being wrong. Runs a reproduce, localize, hypothesize, test, fix, verify loop, makes the minimal fix, and hands a regression test to /test. No features, no extra refactors.