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-architect)<a href="https://agentmods.dev/agents/javiarmesto/aldc-al-development-collection/al-architect"><img src="https://agentmods.dev/badge/agents/javiarmesto/aldc-al-development-collection/al-architect/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/agents/javiarmesto/aldc-al-development-collection/al-architect"><img src="https://agentmods.dev/badge/agents/javiarmesto/aldc-al-development-collection/al-architect.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.00051 | $0.09407 |
| Opus 5 | $0.00026 | $0.04704 |
| Sonnet 5 | $0.00010 | $0.01881 |
| Haiku 4.5 | $0.00005 | $0.00941 |
Grade A, and why
al-architect 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 12d 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 — 1,144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AL Architect Mode - Architecture & Design Assistant
Relationship with al-conductor
al-architect is a strategic design mode, while al-conductor is a tactical implementation orchestrator. They serve different purposes and work together in sequence:
Workflow: al-architect (DESIGN) → al-conductor (IMPLEMENT with TDD)
When to Use al-architect
Use this mode when:
- ✅ Need strategic architectural decisions (patterns, integrations, data models)
- ✅ Want to explore multiple design options interactively
- ✅ Require architectural review of existing solution
- ✅ Planning major refactoring or redesign
- ✅ Need to understand "what pattern should I use?"
- ✅ Designing for scalability, security, or integration
Result: Design documents, architecture diagrams, decision frameworks
When to Use al-conductor
Use al-conductor when:
- ✅ Ready to implement a designed solution with TDD
- ✅ Need structured plan with automatic context gathering (uses agent
al-planning-subagent) - ✅ Want enforced quality gates and code reviews
- ✅ Require documentation trail for complex features
- ✅ Building features that need 3+ AL objects with tests
Result: Implemented code, passing tests, commit-ready changes, complete documentation
Key Differences: al-architect vs agent al-planning-subagent
Both analyze AL codebases, but serve different roles:
| Aspect | al-architect | agent al-planning-subagent |
|---|---|---|
| Purpose | Strategic design consultant | Tactical research assistant |
| Invocation | User switches mode | Called by al-conductor |
| Interaction | Interactive, conversational | Returns structured findings |
| Output | Design options, recommendations | Facts, objects, patterns found |
| Decisions | Makes architectural decisions | Gathers data for decisions |
| Tools | Analysis + Task tool | Analysis only |
| Duration | Extended consultation | Quick focused research |
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.
- 12d ago First seen · 1,144 lines · 51 tokens per session scan A 91537872275c
al-architect is an agent published in the GitHub repository javiarmesto/ALDC-AL-Development-Collection (104 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 9,407 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
PySpark Expert Agent
Diagnose PySpark performance bottlenecks, distributed execution pitfalls, and suggest Spark-native rewrites and safer distributed patterns (incl. mapInPandas guidance).
stackhawk-security-onboarding
Automatically set up StackHawk security testing for your repository with generated configuration and GitHub Actions workflow.
Specification
Generate or update specification documents for new or existing functionality.
SWE
Senior software engineer subagent for implementation tasks: feature development, debugging, refactoring, and testing.
code-reviewer
Senior Android code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, performance. Use for thorough code review before merge.
agentmaster-retro
Transcript-driven analyze-fix-verify loop for the agentmaster skill suite itself. Use after a pipeline run leaves artifacts behind — .transcripts/ snapshots, root-level run transcripts, generated docs, or accumulated telemetry — when the user wants the suite's own skills to keep improving from real usage. Grades…