Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add javiarmesto/ALDC-AL-Development-Collection/plugin install aldcWrote 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-initialize)<a href="https://agentmods.dev/commands/javiarmesto/aldc-al-development-collection/al-initialize"><img src="https://agentmods.dev/badge/commands/javiarmesto/aldc-al-development-collection/al-initialize/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-initialize"><img src="https://agentmods.dev/badge/commands/javiarmesto/aldc-al-development-collection/al-initialize.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.00028 | $0.02895 |
| Opus 5 | $0.00014 | $0.01448 |
| Sonnet 5 | $0.00006 | $0.00579 |
| Haiku 4.5 | $0.00003 | $0.00290 |
Grade A, and why
al-initialize 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 9d 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 — 458 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AL Environment Initialization
Your goal is to initialize the AL development environment and workspace for ${input:ProjectName}.
This workflow covers environment setup, AL workspace configuration, and ALDC rules injection into your project.
Phase 0: ALDC Rules Injection (Plugin Mode)
When ALDC is installed as a Claude Code plugin, path-scoped rules must be copied to the project's .claude/rules/ directory. This phase handles that automatically.
Rules Installation
Copy the following rule templates from the plugin's rules-templates/ directory to your project's .claude/rules/:
# Create project rules directory
mkdir -p .claude/rules
# Copy ALDC rule templates to project
cp "${CLAUDE_PLUGIN_ROOT}/rules-templates/"*.md .claude/rules/
Rules installed:
| Rule | Scope | Purpose |
|---|---|---|
al-guidelines.md |
**/*.al, **/*.json |
Core AL development principles |
al-code-style.md |
**/*.al |
Code formatting and structure |
al-naming-conventions.md |
**/*.al |
Consistent naming patterns |
al-performance.md |
**/*.al |
Performance optimization |
al-error-handling.md |
**/*.al |
Error handling and telemetry |
al-events.md |
**/*.al |
Event-driven development |
al-testing.md |
**/test/**/*.al |
Test implementation patterns |
al-agent-toolkit.md |
**/*.al |
AI Development Toolkit patterns |
CLAUDE.md Generation
Generate a project-level CLAUDE.md that references ALDC:
# ${input:ProjectName} — Claude Code Instructions
## Framework
This project uses **ALDC** (AL Development Collection) plugin for Claude Code.
All agents, skills, and workflows are available via the `aldc:` namespace.
## Quick Start
- `/aldc:al-spec-create` — Create specifications
- `/aldc:al-build` — Build extension
- `agent "aldc:al-architect"` — Architecture design
- `agent "aldc:al-developer"` — Implementation
## Project-Specific Notes
[Add your project-specific instructions here]
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.
- 9d ago First seen · 458 lines · 28 tokens per session scan A e38253e85bcd
al-initialize is a command published in the GitHub repository javiarmesto/ALDC-AL-Development-Collection (103 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 2,895 once invoked, about $0.0001 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.