al-code-review

al-code-review is a skill for Claude Code, Codex from microsoft/BCQuality. It costs 46 tokens per session (932 once invoked), scanned A, original, MIT.

A skill that reviews Microsoft Dynamics 365 Business Central AL code using BCQuality rules. AL is the programming language used to customise Business Central.

In plain words
What is it for?
Use it to review AL changes, a working-tree diff, a branch, or one AL file when BCQuality is installed.
Why use it?
It gives pull requests, diffs, branches, and individual files a focused review against Business Central-specific quality rules.

Skill for Claude CodeCodex ✓ vendor

Written for no agent in particular: nothing here depends on one.

Good fit Use it to review AL changes, a working-tree diff, a branch, or one AL file when BCQuality is installed.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/microsoft/bcquality/al-code-review
About the project

microsoft/BCQuality is a structured knowledge base and skills library for Microsoft Business Central development. It records Business Central-specific rules and platform behaviors that coding agents or developers might otherwise get wrong. The catalogue entries provide the agents and skill that consume this guidance.

microsoft/BCQuality · 231 stars · on GitHub

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.

Any agent
npx skills add microsoft/BCQuality --skill al-code-review
Clone the repo
git clone --depth 1 https://github.com/microsoft/BCQuality

Made for: Claude Code, Codex.

Its marketplace also offers this one on its own, as the plugin bcquality — /plugin install bcquality after adding the marketplace above.

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-code-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/microsoft/bcquality/al-code-review/github.svg)](https://agentmods.dev/skills/microsoft/bcquality/al-code-review)
Your own site
<a href="https://agentmods.dev/skills/microsoft/bcquality/al-code-review"><img src="https://agentmods.dev/badge/skills/microsoft/bcquality/al-code-review/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.

agentmods 80×15 button for al-code-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/microsoft/bcquality/al-code-review"><img src="https://agentmods.dev/badge/skills/microsoft/bcquality/al-code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 932 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Agent Snooping · line 17
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
How audits are shown
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.00046 $0.00932
Opus 5.5 $0.00018 $0.00373
Sonnet 5.5 $0.00009 $0.00186
Haiku 4.5 $0.00005 $0.00093

Measured 1mo ago against content hash dec4e92b6de4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

al-code-review 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.

skills/al-code-review/SKILL.md · 72 lines

How it starts

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

AL code review

This is BCQuality's host-native adapter for standalone plugin installations. It is not a BCQuality action skill and contains no review or routing policy. Its only responsibility is to translate the caller's request into an Entry task context and execute the resulting dispatch.

Execute

  1. Resolve PLUGIN_ROOT to the directory containing this plugin's root plugin.json. This file is PLUGIN_ROOT/skills/al-code-review/SKILL.md; when the host does not expose the plugin root, resolve it two levels above this file.
  2. Build the task-context required by PLUGIN_ROOT/skills/entry.md:
    • Copy the caller's actual request verbatim into goal; do not replace a focused request such as "review performance" with a generic full-review goal.
    • Set inputs-available to the inputs actually available to the review: folder-path for an app or source folder, pr-diff for changes, or file-path for one file. Pass the caller's actual path with the selected input type; for a whole-app request in the current working directory, use that directory as the folder-path.
    • Set technologies: [al] when the input is known to be AL.
    • Pass bc-version, countries, and application-area only when supplied or reliably determined.
    • If BCQUALITY_ENABLED_LAYERS is set, split its comma-separated value and pass the trimmed, non-empty entries as enabled-layers; otherwise omit the field and let Entry apply its default.
    • If BCQUALITY_DISABLED_SKILLS is set, split its comma-separated value and pass the trimmed, non-empty entries as disabled-skills; otherwise omit the field.
  3. Read and execute PLUGIN_ROOT/skills/entry.md exactly as written, including its Preparation step. Entry is authoritative for index freshness, routing, defaults, and failure behavior; this adapter must not duplicate or weaken those rules. Entry is written for a checkout whose root is the current directory, so resolve every repo-relative path it names against PLUGIN_ROOT rather than the caller's working directory, which is the user's own project. In particular, run Preparation's index build as pwsh PLUGIN_ROOT/tools/Build-KnowledgeIndex.ps1: the generator resolves its own root and writes PLUGIN_ROOT/knowledge-index.json, which is not shipped and is therefore absent on a fresh install. If pwsh is unavailable or the build fails, continue — READ falls back to path-based discovery — but do not treat a failed build as a failed review.
  4. Follow Entry's How the agent uses the dispatch instructions. Invoke only the returned action skills, pass each dispatch entry's exact input subset, and read PLUGIN_ROOT/skills/read.md and PLUGIN_ROOT/skills/do.md on demand. When a dispatched super-skill requests isolated leaf execution and the host supports child contexts, use them.
  5. Return each dispatched action skill's findings report unchanged. If Entry returns no-match or failed, return its dispatch record unchanged.

Read the full file on GitHub · 72 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. 1mo ago Changed · +2 lines · +2 tokens per session dec4e92b6de4
  2. 1mo ago First seen · 70 lines · 44 tokens per session scan A b0db3f49fdb1

Subscribe to this mod's changes

al-code-review is a skill published in the GitHub repository microsoft/BCQuality (231 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 932 once invoked, about $0.0002 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-09-03.

Related

Other skills, from other repositories

autoreview

Structured code review through the shared OpenClaw agent-skills installation.

openclaw/clawhub · 17 tokens

omh-code-review

This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 48 tokens

revdiff-plan

Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…

umputun/revdiff · 84 tokens

asplos-writing-style

Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…

brycewang-stanford/Awesome-Journal-Skills · 65 tokens

explore-unknowns

Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…

dzhng/skills · 162 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens