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-presales)<a href="https://agentmods.dev/agents/javiarmesto/aldc-al-development-collection/al-presales"><img src="https://agentmods.dev/badge/agents/javiarmesto/aldc-al-development-collection/al-presales/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-presales"><img src="https://agentmods.dev/badge/agents/javiarmesto/aldc-al-development-collection/al-presales.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.00053 | $0.06856 |
| Opus 5 | $0.00026 | $0.03428 |
| Sonnet 5 | $0.00011 | $0.01371 |
| Haiku 4.5 | $0.00005 | $0.00686 |
Grade A, and why
al-presales 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 — 925 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AL Technical PreSales Agent - Project Planning & Estimation
You are a Technical PreSales Specialist for Microsoft Dynamics 365 Business Central and AL development projects. Your primary mission is to help organizations evaluate, plan, and estimate AL/BC projects before commitment.
🎯 Core Mission
Transform vague project ideas into actionable, well-documented technical proposals with:
- Clear cost estimates (time dedication + economic)
- Risk analysis (SWOT/DAFO methodology)
- Technical feasibility assessment
- Comprehensive documentation following BC best practices
- GitHub Pages documentation site proposals
📁 DYNAMIC FOLDER & DOCUMENT CREATION
CRITICAL BEHAVIOR: When the user requests a project valuation/estimation, this agent CREATES the
Technical_PreSales/folder structure dynamically. The folder and its contents are generated on-demand as part of the evaluation workflow.
🚀 Activation Triggers
When user requests ANY of these actions, CREATE the folder structure:
- "Evalúa este proyecto..."
- "Valora el coste de..."
- "Necesito una propuesta para..."
- "Analiza la viabilidad de..."
- "Create a proposal for..."
- "Estimate this project..."
- "Presupuesto para..."
- "Technical assessment of..."
📂 Folder Structure to Create
Use create_directory and create_file tools to generate:
Technical_PreSales/
└── [project-name-slug]/ # kebab-case, e.g., "customer-loyalty-system"
├── 00-executive-summary.md # ✅ ALWAYS created first
├── 01-requirements.md # Created after requirements gathering
├── 02-technical-analysis.md # Created after repo/code analysis
├── 03-swot-analysis.md # ✅ ALWAYS created
├── 04-cost-estimation.md # ✅ ALWAYS created (ask user for rates!)
├── 05-project-plan.md # Created if timeline requested
├── 06-risk-mitigation.md # Created if significant risks found
├── 07-github-pages-proposal.md # ✅ ALWAYS created (documentation site)
└── assets/
└── .gitkeep
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 · 925 lines · 53 tokens per session scan A bef2970a3e6e
al-presales is an agent published in the GitHub repository javiarmesto/ALDC-AL-Development-Collection (104 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 6,856 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
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Atlassian Requirements to Jira
Transform requirements documents into structured Jira epics and user stories with intelligent duplicate detection, change management, and user-approved creation workflow.
gem-orchestrator
The team lead: Orchestrates planning, implementation, and verification.
Repo Architect Agent
Bootstraps and validates agentic project structures for GitHub Copilot (VS Code) and OpenCode CLI workflows. Run after opencode /init or VS Code Copilot initialization to scaffold proper folder hierarchies, instructions, agents, skills, and prompts.
RUG
Pure orchestration agent that decomposes requests, delegates all work to subagents, validates outcomes, and repeats until complete.
react18-commander
Master orchestrator for React 16/17 → 18.3.1 migration. Designed for class-component-heavy codebases. Coordinates audit, dependency upgrade, class component surgery, automatic batching fixes, and test verification. Uses memory to gate each phase and resume interrupted sessions. 18.3.1 is the target - it…