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-pr-prepare)<a href="https://agentmods.dev/commands/javiarmesto/aldc-al-development-collection/al-pr-prepare"><img src="https://agentmods.dev/badge/commands/javiarmesto/aldc-al-development-collection/al-pr-prepare/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-pr-prepare"><img src="https://agentmods.dev/badge/commands/javiarmesto/aldc-al-development-collection/al-pr-prepare.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.00037 | $0.02456 |
| Opus 5.5 | $0.00015 | $0.00982 |
| Sonnet 5.5 | $0.00007 | $0.00491 |
| Haiku 4.5 | $0.00004 | $0.00246 |
Grade A, and why
al-pr-prepare 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 1mo 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 — 381 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot CLI adapter — generated; do not edit this distribution. Select a role using /agent or copilot --agent . Role names in this contract are routing destinations, never chat mentions or evidence of an invocation. Delegate only through the native task tool, using the exact discovered agent ID as agent_type (for example al-planning-subagent). Inspect list_agents and the actual task schema first. Keep all canonical human gates. Pass bounded context inline; wait for completion (read_agent for a background task) before consuming the result. A delegated role returns questions to its caller for the human gate. If task or the requested custom agent is unavailable in this context, return the blocked handoff to the caller/user. Never impersonate a missing subagent, silently substitute general-purpose, or launch another CLI process to fake it. Tool aliases in frontmatter select capabilities; call the actual tools exposed by the host: view, glob, grep/rg, edit/create/apply_patch, bash/powershell, web_fetch, task. Use a capability only when granted to this role and available. Load domain skills through the host's skill mechanism when exposed, otherwise read the complete bundled SKILL.md. A read is not a native skill invocation. Resolve PLUGIN_ROOT to this installed agent's plugin directory (not the project or original checkout). It is a path placeholder here, not a promised global shell variable. Read docs/copilot-cli-al-tooling.md there for LSP/MCP bindings; it supersedes older availability examples in the shared terminal contract at skills/skill-migrate/references/cli-al-tools.md, never role duties or human gates. Project instructions and matching .github/instructions rules remain binding; pass the relevant excerpts to delegated roles. Canonical artifacts remain in .github/plans/. Role write scopes are behavioral, not filesystem sandboxes. AL execution requires a verified terminal command/runner or an actually exposed MCP capability. Reuse the configured AL LSP for Agents wrapper through native CLI semantic tools when exposed to this role. Inspect the catalog; do not invent tool aliases or broaden read-only grants to enable rename/write operations. Editor debugger controls remain separate from semantic navigation. Official AL MCP selectors use al/; only Developer/Implementer receive compile/build/ restore. Discover the actual callable names and pass the correct App/Test path. No official publish/authentication tool is granted by this adapter. Triage alone receives the optional dedicated bc-profiling and bc-snapshot proxies; discover their schemas and confirm an authorized target/window before capture. Other roles consume evidence. Capture does not prove autonomous snapshot debugging. Symbol MCP: before any tools/call, verify AL CLI prerequisites are already provisioned; this provider may auto-install AL tools on first use. A read-only role must return that prerequisite to the caller, never bootstrap software. Load symbols via al_packages(action: load, path: absolute consumer path). The MCP process may run from the plugin cache; never assume its cwd is the consumer. Use the discovered schema and report missing .app packages explicitly. Record missing capabilities and unexecuted checks explicitly; never simulate.
AL Pull Request Preparation
Your goal is to prepare a pull request draft for the branch <Branch from $ARGUMENTS> summarizing all modifications, test evidence, and validation steps.
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.
- 1mo ago Changed · +11 lines 8b091a70c69d
- 1mo ago Changed · +35 lines 012463786fad
- 1mo ago Changed · -15 lines · -2 tokens per session 6e6837121adf
- 1mo ago Changed · +12 lines 63da3eb74546
- 1mo ago Changed · -4 lines 0e2bcae8cab1
- 1mo ago First seen · 342 lines · 39 tokens per session scan A ac6f9d46402e
al-pr-prepare is a command published in the GitHub repository javiarmesto/ALDC-AL-Development-Collection (113 stars, last pushed 4d ago), licensed MIT. It adds 37 tokens to every session and 2,456 once invoked, about $0.0001 per session on Opus 5.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
elegant-code-review
Review the current working diff against the elegant-code decision ladder and propose deletions, honoring the negligence floor.
prp-commit
Quick commit with natural language file targeting: describe what to commit in plain English.
validate-pr-description
Use when validating a PR title and description for conventional commit format, issue linking keywords, and template compliance before submission.
karpathy-check
Revisa as alterações em stage (ou o último commit) com base nos 4 princípios de codificação do Karpathy. Verifica complexidade, ruído no diff, suposições ocultas e verificação de objetivos. Uso: /karpathy-check [--last-commit].
review
Review code against project rules using the code-reviewer agent.
fix-comments
Address PR review comments by implementing requested changes automatically.