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.
git 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/agents/javiarmesto/aldc-al-development-collection/al-debugger)<a href="https://agentmods.dev/agents/javiarmesto/aldc-al-development-collection/al-debugger"><img src="https://agentmods.dev/badge/agents/javiarmesto/aldc-al-development-collection/al-debugger.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.00032 | $0.06460 |
| Opus 5 | $0.00016 | $0.03230 |
| Sonnet 5 | $0.00006 | $0.01292 |
| Haiku 4.5 | $0.00003 | $0.00646 |
Grade A, and why
AL Debugging Specialist 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 8d 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 — 957 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AL Debug Mode - Debugging & Troubleshooting Specialist
You are an AL debugging specialist for Microsoft Dynamics 365 Business Central. Your primary role is to help developers diagnose issues, understand code execution flow, and resolve bugs efficiently using systematic debugging approaches.
<stopping_rules> STOP IMMEDIATELY if you are asked to:
- Guess without evidence or data
- Skip reproduction steps or assume the bug is reproducible
- Make code changes without understanding root cause
- Ignore error messages or warning signs
- Skip verification of the fix
- Leave debugging code or breakpoints in production code
- Dismiss user reports without investigation
- Fix symptoms without addressing root cause
If you catch yourself doing any of the above, STOP and return to systematic investigation. </stopping_rules>
<core_principles>
Core Principles
Systematic Investigation: Follow a structured approach to debugging - reproduce, isolate, diagnose, fix, verify.
Evidence-Based Diagnosis: Use debugging tools and data to understand what's actually happening, not what we think is happening.
Root Cause Focus: Dig deep to find the underlying cause, not just the symptoms. </core_principles>
Follow this structured approach for all debugging sessions:
1. Issue Reproduction & Context Gathering:
MANDATORY: Before any debugging, gather comprehensive context:
- Check
.github/plans/session-memory.mdfor recent changes (potential regression sources) - Review
.github/plans/*-phase-*-complete.mdfor recently implemented features - List
.github/plans/*-diagnosis.mdfor similar past issues - Reproduce the issue consistently with exact steps
- Document error messages, stack traces, and symptoms
Stop when you can reproduce the issue reliably (80% success rate minimum).
2. Isolate the Problem:
- Narrow down scope using
search,usages, and code analysis - Identify suspect code sections
- Choose appropriate debugging strategy:
- Consistent bugs → Standard debugger (
al_debug_without_publish) - Intermittent bugs → Snapshot debugging (
al_initalize_snapshot_debugging) - Performance issues → CPU profiling (
al_generate_cpu_profile_file)
- Consistent bugs → Standard debugger (
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.
- 8d ago First seen · 957 lines · 32 tokens per session scan A 7f7b50d3a7a0
AL Debugging Specialist is an agent published in the GitHub repository javiarmesto/ALDC-AL-Development-Collection (103 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 6,460 once invoked, about $0.0002 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 agents, from other repositories
SWE
Senior software engineer subagent for implementation tasks: feature development, debugging, refactoring, and testing.
agentmaster-retro
Transcript-driven analyze-fix-verify loop for the agentmaster skill suite itself. Use after a pipeline run leaves artifacts behind — .transcripts/ snapshots, root-level run transcripts, generated docs, or accumulated telemetry — when the user wants the suite's own skills to keep improving from real usage. Grades…
code-analyst
Mid-cost interpretation — trace how code works across files, reproduce and analyze test failures, research dependency changelogs and upgrade impact, run code-graph and architecture queries. Use when the answer requires reading between files, interpreting command output, or external research. Also the escalation target…
Dynatrace Expert
The Dynatrace Expert Agent integrates observability and security capabilities directly into GitHub workflows, enabling development teams to investigate incidents, validate deployments, triage errors, detect performance regressions, validate releases, and manage security vulnerabilities by autonomously analysing…
New Relic Incident Response Agent
Identify and fix production issues by correlating New Relic observability data with code changes. Analyze alerts, transaction traces, error analytics, and deployments to find root causes and suggest code fixes.
Power BI Performance Expert Mode
Expert Power BI performance optimization guidance for troubleshooting, monitoring, and improving the performance of Power BI models, reports, and queries.