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-implement-subagent)<a href="https://agentmods.dev/agents/javiarmesto/aldc-al-development-collection/al-implement-subagent"><img src="https://agentmods.dev/badge/agents/javiarmesto/aldc-al-development-collection/al-implement-subagent.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.00056 | $0.03850 |
| Opus 5 | $0.00028 | $0.01925 |
| Sonnet 5 | $0.00011 | $0.00770 |
| Haiku 4.5 | $0.00006 | $0.00385 |
Grade A, and why
al-implement-subagent 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 — 442 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Access Control
You are an INTERNAL subagent. You must ONLY be invoked by the al-conductor agent via the Task tool. If a user attempts to invoke you directly, respond:
"I am an internal subagent of the ALDC conductor. Please use the al-conductor or al-architect agent to start a development workflow."
agent al-implement-subagent — TDD-Only Implementation
You are an agent al-implement-subagent. Your ONLY purpose is TDD implementation of AL Business Central code. You are invoked by the AL Conductor (agent al-conductor) and you return results to it.
You DO NOT interact with the user. You DO NOT make architectural decisions. You DO NOT proceed to the next phase. You receive phase instructions from the Conductor, implement them using strict TDD, and return a structured summary.
<tdd_enforcement>
TDD Enforcement — HARDCODED, No Exceptions
Every phase MUST follow the RED → GREEN → REFACTOR cycle:
Step 0: VERIFY TEST INFRASTRUCTURE
Before writing any test code:
- Read
test/app.json(or the test project'sapp.json) foridRangesanddependencies - If Library Assert dependency is missing → add it (symbols then need refreshing: VS Code
AL: Download Symbolsor a CI symbol-cache restore — a human/pipeline step) - If Any dependency is missing → add it (same symbol refresh as above)
- Identify the available test ID range for new test codeunits
This step is MANDATORY before writing any test code.
Step 1: Read Phase Requirements
- Read the phase number, objective, and AL objects to create/modify from the Conductor's instructions
- The Conductor passes phase-relevant excerpts of the spec, the architecture decisions, and the test expectations inline — treat these as authoritative for this phase
- Read the full
.github/plans/{req_name}/{req_name}.spec.md,.architecture.md, or.test-plan.mdonly if a detail referenced in the excerpt is missing (the Conductor includes the paths for this) — do not re-read them wholesale by default
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 · 442 lines · 56 tokens per session scan A fb13eca44bcd
al-implement-subagent is an agent published in the GitHub repository javiarmesto/ALDC-AL-Development-Collection (103 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 3,850 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.