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/plugins/javiarmesto/aldc-al-development-collection/claude-plugin)<a href="https://agentmods.dev/plugins/javiarmesto/aldc-al-development-collection/claude-plugin"><img src="https://agentmods.dev/badge/plugins/javiarmesto/aldc-al-development-collection/claude-plugin/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/plugins/javiarmesto/aldc-al-development-collection/claude-plugin"><img src="https://agentmods.dev/badge/plugins/javiarmesto/aldc-al-development-collection/claude-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
aldc 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 5d 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.
What it actually says
{
"name": "aldc",
"displayName": "ALDC for Claude Code",
"version": "5.1.1",
"description": "AI-Native AL Development Collection for Microsoft Dynamics 365 Business Central. Agents (architect, developer, conductor, pre-sales, agent-builder, triage, dredd) + TDD subagents, skills, and workflows for extension-only development with TDD, BCQuality-cited review/audit, event-driven architecture, and HITL gates.",
"author": {
"name": "javiarmesto",
"url": "https://github.com/javiarmesto"
},
"homepage": "https://github.com/javiarmesto/ALDC-AL-Development-Collection",
"repository": "https://github.com/javiarmesto/ALDC-AL-Development-Collection",
"license": "MIT",
"keywords": [
"AL",
"Business Central",
"Dynamics 365",
"ERP",
"extension-development",
"TDD",
"event-driven",
"Microsoft",
"architecture",
"testing",
"API",
"debugging"
],
"mcpServers": {
"al-symbols-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"[email protected]"
]
},
"context7": {
"type": "http",
"url": "https://mcp.context7.com/mcp"
},
"microsoft-docs": {
"type": "http",
"url": "https://learn.microsoft.com/api/mcp"
}
},
"userConfig": {
"bcSandboxUrl": {
"type": "string",
"title": "BC Sandbox URL",
"description": "URL of your Business Central sandbox environment (e.g., https://businesscentral.dynamics.com/your-tenant)",
"sensitive": false
},
"publisherName": {
"type": "string",
"title": "Publisher Name",
"description": "Your extension publisher name for app.json",
"sensitive": false
}
}
}
What it installs
The manifest is a name and a version. 2 hooks travel with it, and installing the plugin installs all of them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago Changed · -1 lines 0bd307628ac5
- 18d ago Changed ab1251e796f6
- 19d ago Changed 901d535bdf3b
- 1mo ago Changed 82b13af3bd22
- 1mo ago Changed · +5 lines 9b52eef2f91c
- 1mo ago First seen · 56 lines scan A 69f86d239d0f
aldc is a plugin published in the GitHub repository javiarmesto/ALDC-AL-Development-Collection (112 stars, last pushed 3d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
backend-development
Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development.
probity
TDD enforcement and guardrails for Claude Code, Codex, and GitHub Copilot CLI.
backend-development
Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development.
rails-toolkit
Complete Rails development workflow with TDD, security reviews, and Linear integration.
backend-development
Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development.
pdlc
Turn AI software engineering into an auditable, on-disk state machine. A staged PDLC workflow (PRD, design, TDD, implement, review, ship, retro) enforces hard contracts — artifacts on disk, per-feature state machine, tests-before-code, objective checks from real command exit codes, single-shot auto-repair — so AI work.