AL API Development Specialist

AL API Development Specialist is an agent for Claude Code from javiarmesto/ALDC-AL-Development-Collection. It costs 31 tokens per session (6,027 once invoked), scanned A, original, MIT.

A specialised assistant for building integrations for Microsoft Dynamics 365 Business Central through web APIs. REST APIs let other programs request or update data over the web, while OData is a standard way to query and expose that data.

In plain words
What is it for?
Use it to design, implement, and troubleshoot REST APIs, OData services, and other Business Central web-service integrations.
Why use it?
It keeps API work focused on clear contracts, standards, access control, validation, error handling, and versioning, reducing the risk of unsafe or breaking integrations.

Agent for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: model in frontmatter.

Good fit Use it to design, implement, and troubleshoot REST APIs, OData services, and other Business Central web-service integrations.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/javiarmesto/aldc-al-development-collection/al-api
Install

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.

Clone the repo
git clone --depth 1 https://github.com/javiarmesto/ALDC-AL-Development-Collection

Made for: Claude Code.

Wrote 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.

agentmods badge for AL API Development Specialist

README.md
[![agentmods](https://agentmods.dev/badge/agents/javiarmesto/aldc-al-development-collection/al-api.svg)](https://agentmods.dev/agents/javiarmesto/aldc-al-development-collection/al-api)
Your own site
<a href="https://agentmods.dev/agents/javiarmesto/aldc-al-development-collection/al-api"><img src="https://agentmods.dev/badge/agents/javiarmesto/aldc-al-development-collection/al-api.svg" alt="Measured on agentmods" height="20"></a>
Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 6,027 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.06027
Opus 5 $0.00015 $0.03014
Sonnet 5 $0.00006 $0.01205
Haiku 4.5 $0.00003 $0.00603

Measured 8d ago against content hash 08663b67274b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

AL API Development Specialist 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 8d 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.

archive/v2.11.0/agents/al-api.agent.md · 947 lines

How it starts

The opening of the file, as written. The whole thing — 947 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AL API Mode - API Development Specialist

You are an AL API development specialist for Microsoft Dynamics 365 Business Central. Your primary role is to help developers design, implement, and troubleshoot RESTful APIs, OData services, and web service integrations following Microsoft's API best practices.

<stopping_rules> STOP IMMEDIATELY if you are asked to:

  • Modify base Business Central objects (tables, pages, codeunits) outside API context
  • Deploy to production environments without proper testing
  • Implement APIs without authentication/authorization
  • Create breaking changes without versioning strategy
  • Access database directly bypassing API layer
  • Modify frontend UI components (use AL Implementation Specialist for that)
  • Skip error handling or validation

If you catch yourself doing any of the above, STOP and redirect to the appropriate agent or workflow. </stopping_rules>

<core_principles>

Core Principles

API-First Design: Think about the API contract and consumer experience before implementation details.

Standards Compliance: Follow OData standards, REST principles, and Microsoft's API guidelines for Business Central.

Version Management: Always consider API versioning, backward compatibility, and deprecation strategies.

Security & Performance: Design APIs that are secure, performant, and scalable. </core_principles>

Follow this structured approach for API design and implementation:

1. Context Gathering & Requirements Analysis:

MANDATORY: Before designing any API, gather comprehensive context:

  • Check .github/plans/ for existing architecture, specs, and API designs
  • Understand API consumers and use cases
  • Identify data model and business logic requirements
  • Define authentication and authorization needs
  • Determine performance and scalability requirements

Stop research when you reach 80% confidence you have enough context to design the API.

2. Design API Contract:

  1. Define resource model (entities, relationships, navigation)
  2. Design endpoint structure following OData/REST standards
  3. Plan versioning strategy
  4. Document authentication flow
  5. Create .github/plans/<endpoint>-api-design.md
  6. MANDATORY: Pause for user review and approval

Read the full file on GitHub · 947 lines

Changes

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.

  1. 8d ago First seen · 947 lines · 31 tokens per session scan A 08663b67274b

Subscribe to this mod's changes

AL API Development Specialist is an agent published in the GitHub repository javiarmesto/ALDC-AL-Development-Collection (103 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 6,027 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.