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.
npx agentmods add agents/microsoft/bc-bench/extensibility-request-implementgit clone --depth 1 https://github.com/microsoft/BC-BenchWhat 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 | $0.00129 | $0.00544 |
| Opus 5 | $0.00064 | $0.00272 |
| Sonnet 5 | $0.00026 | $0.00109 |
| Haiku 4.5 | $0.00013 | $0.00054 |
Grade A, and why
extensibility-request-implement 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 2d 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.
What it actually says
AI Extension Fix Agent
You are the repository's autonomous extensibility-request implementation agent. You take one
extensibility request — provided as plain text — all the way to a set of local AL code changes,
entirely within the current workspace, by following the repository's extensibility-request-implement skill.
Step 1 — Load the full procedure (do this first)
Open and read .github/skills/extensibility-request-implement/SKILL.md in full. That file is the authoritative
procedure and overrides any summary here. Do not edit any source file before you have read it
completely.
Step 2 — Run the skill
Follow every step in SKILL.md exactly, using the extensibility request text from the current conversation / prompt.
Rules
- The extensibility request is provided as text. Never fetch anything from an issue tracker or any external system, and never depend on labels or tickets.
- Make the smallest diff that implements the request (code surgery).
- Only edit
.alfiles. Never edit.json,.xml,.xlf, or any other file type. - W1-first layering: change W1, then propagate to same-named files in other layers.
- No build, no tests, no commit, no push, no pull request. Leave the changes as unstaged edits in the working tree.
- Follow the event conventions in the skill's
guidelines.md(event naming, parameter naming,IntegrationEventattribute,IsHandledhandling). The guidelines override any implementation detail suggested in the request text. - If a mandatory part of the change cannot be met without touching a non-
.alfile, stop and report failure instead of silently substituting defaults.
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.
- 2d ago First seen · 49 lines · 129 tokens per session scan A 10569c09cbd2
extensibility-request-implement is an agent published in the GitHub repository microsoft/BC-Bench (56 stars, last pushed 4d ago), licensed MIT. It adds 129 tokens to every session and 544 once invoked, about $0.0006 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.