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/commands/javiarmesto/aldc-al-development-collection/al-build)<a href="https://agentmods.dev/commands/javiarmesto/aldc-al-development-collection/al-build"><img src="https://agentmods.dev/badge/commands/javiarmesto/aldc-al-development-collection/al-build/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/commands/javiarmesto/aldc-al-development-collection/al-build"><img src="https://agentmods.dev/badge/commands/javiarmesto/aldc-al-development-collection/al-build.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.00032 | $0.00760 |
| Opus 5 | $0.00016 | $0.00380 |
| Sonnet 5 | $0.00006 | $0.00152 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
al-build 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build and Deploy AL Extension
Your goal is to build (compile + package) the AL extension for the ${input:DeploymentType} environment and to guide its deployment.
What runs where. In the Claude Code harness you compile and package with the AL command-line tool (ALTool /
al) viaBash. ALTool has no publish/test verb — deployment and test runs are VS Code (AL: Publish/AL: Run Tests) or AL-Go/CI pipeline steps. So this command builds the.appand then hands off the deploy with a clear, approved checklist.
Select Deployment Strategy
Inspect the project (Read app.json, Grep/Glob, al-symbols-mcp for dependencies) and select the appropriate deployment strategy.
Ask and confirm with the user before proceeding.
Deployment Types
Based on the deployment type, use the appropriate strategy:
Development Environment
- Build:
Bash: al compile(single project) oral workspace compile(multi-project) to produce the.app - Review: Present compiler results for human approval
- Deploy: hand off to VS Code
AL: Publish with RADfor rapid iteration (requires approval) - Verify: Read the compiler output for any errors
Testing Environment
- Build:
Bash: al compilewith full validation (read all warnings/errors) - Package: the
.appis produced byal compile - Review: Present package details for human approval
- Deploy: hand off to VS Code
AL: Publish(debugging enabled) or the CI pipeline (requires approval) - Test: ask the human to run VS Code
AL: Run Tests(or the CI test runner) and confirm all unit tests pass
Production Environment
- Build:
Bash: al compilewith strict validation - Package: take the release
.appproduced byal compile - Validation: Verify package integrity and dependencies (
app.json+ al-symbols-mcpal_packages) - Documentation: Generate deployment checklist and present for review
- Human Gate: MANDATORY - Manual approval required before any production action
- Note: Automated deployment to production is intentionally disabled as safeguard
- All production changes require explicit human authorization, run through the AL-Go/CI release pipeline or VS Code
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 · 67 lines · 32 tokens per session scan A 3e4d2f4b3525
al-build is a command published in the GitHub repository javiarmesto/ALDC-AL-Development-Collection (104 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 760 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 commands, from other repositories
ship
Run the Android pre-launch checklist via parallel fan-out to specialist personas, then synthesize a go/no-go decision with rollback and staged rollout plan.
code-simplify
Simplify code incrementally while preserving behavior exactly.
test
Write tests before implementation using Red-Green-Refactor.
spec
Write a structured specification before writing any code.
review-skill
Review one skill for standalone packaging, instruction quality, contradictory guidance, resource correctness, and current best practices.
review-workflow
Review one workflow folder for standalone packaging, Copilot customisation quality, local link correctness, and current best practices.