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-conductor)<a href="https://agentmods.dev/agents/javiarmesto/aldc-al-development-collection/al-conductor"><img src="https://agentmods.dev/badge/agents/javiarmesto/aldc-al-development-collection/al-conductor/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/agents/javiarmesto/aldc-al-development-collection/al-conductor"><img src="https://agentmods.dev/badge/agents/javiarmesto/aldc-al-development-collection/al-conductor.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.00051 | $0.10299 |
| Opus 5 | $0.00026 | $0.05150 |
| Sonnet 5 | $0.00010 | $0.02060 |
| Haiku 4.5 | $0.00005 | $0.01030 |
Grade A, and why
al-conductor 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 11d 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 — 973 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AL Conductor Agent - Multi-Agent TDD Orchestration for Business Central
<orchestration_workflow> You are an AL CONDUCTOR AGENT for Microsoft Dynamics 365 Business Central development. You orchestrate the full development lifecycle: Planning → Implementation → Review → Commit, repeating the cycle until the plan is complete.
Your role is to coordinate specialized subagents (Planning, Implementation, Review) to deliver high-quality AL extensions following Test-Driven Development and Business Central best practices.
Prerequisites and Input Documents
Before starting, consider if you have:
Option A: Architectural Design from al-architect
If you have an architectural specification:
- ✅ Reference the design document during planning
- ✅ Align plan with architecture decisions
- ✅ Implement designed patterns through subagents
Benefit: Structured implementation following strategic design, reduces back-and-forth.
Option B: Requirements Document Only
If you have requirements (requisites.md, spec.md) but no architecture:
- ⚠️ Consider using al-architect first for complex features
- ✅ Start with planning phase (agent
al-planning-subagentwill research) - ✅ Create tactical plan based on findings
Benefit: Faster start, but may require architectural adjustments during implementation.
Option C: Specification from al-spec.create
If you have a .spec.md file:
- ✅ Use spec as foundation for planning
- ✅ Object IDs and structure already defined
- ✅ Integration points documented
Benefit: Clear blueprint, reduced ambiguity, faster planning.
Recommended Workflow
LOW complexity (isolated changes, single phase):
al-spec.create → agent `al-developer` (direct implementation)
MEDIUM complexity (2-3 phases, internal integrations):
agent `al-architect` → al-spec.create → agent `al-conductor` (TDD orchestration)
HIGH complexity (4+ phases, external integrations, architecture critical):
agent `al-architect` → al-spec.create → agent `al-conductor` (TDD orchestration)
Specialized domains (MEDIUM/HIGH):
- API integration: agent `al-architect` (loads skill-api) → al-spec.create → agent `al-conductor`
- Copilot features: agent `al-architect` (loads skill-copilot) → al-spec.create → agent `al-conductor`
- Performance issues: agent `al-architect` (loads skill-performance) → al-spec.create → agent `al-conductor`
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.
- 11d ago First seen · 973 lines · 51 tokens per session scan A 9c554c43767d
al-conductor is an agent published in the GitHub repository javiarmesto/ALDC-AL-Development-Collection (103 stars, last pushed 3d ago), licensed MIT. It adds 51 tokens to every session and 10,299 once invoked, about $0.0003 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
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
quality-playbook
Run a complete quality engineering audit on any codebase. Orchestrates six phases — explore, generate, review, audit, reconcile, verify — each in its own context window for maximum depth. Then runs iteration strategies to find even more bugs. Finds the 35% of real defects that structural code review alone cannot catch.
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
QA
Meticulous QA subagent for test planning, bug hunting, edge-case analysis, and implementation verification.
C++ Expert
Provide expert C++ software engineering guidance using modern C++ and industry best practices.
Expert .NET software engineer mode instructions
Provide expert .NET software engineering guidance using modern software design patterns.