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 skills/loacher-solution/bc-agent-plugin/bc-bootstrapnpx skills add loacher-solution/bc-agent-plugin --skill bc-bootstrapgit clone --depth 1 https://github.com/loacher-solution/bc-agent-pluginWrote 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/skills/loacher-solution/bc-agent-plugin/bc-bootstrap)<a href="https://agentmods.dev/skills/loacher-solution/bc-agent-plugin/bc-bootstrap"><img src="https://agentmods.dev/badge/skills/loacher-solution/bc-agent-plugin/bc-bootstrap.svg" alt="Measured on agentmods" 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 | $0.00064 | $0.01049 |
| Opus 5 | $0.00032 | $0.00524 |
| Sonnet 5 | $0.00013 | $0.00210 |
| Haiku 4.5 | $0.00006 | $0.00105 |
Grade A, and why
bc-bootstrap 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 4d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bc-bootstrap
First-run setup for a Business Central AL project. Idempotent: running it twice is a no-op if everything is already in place.
When to use
- The user opens a folder with
app.jsonbut no.mcp.jsonentry foralmcp. - The user says "set up Claude for this BC project" or similar.
- Another BC skill fails with "AL toolchain not found".
Steps
Run these steps in order, using the Bash tool to invoke the PowerShell scripts.
1. Verify app.json exists
If there is no app.json at the project root, stop and tell the user: "Run this from a Business Central project root (the folder containing app.json)."
2. Check that PowerShell 7 is installed
pwsh -NoProfile -File <plugin>/skills/bc-bootstrap/scripts/ensure-pwsh7.ps1
If the result is status: "missing" or "outdated", ask the user whether to install PowerShell 7 via winget: winget install --id Microsoft.PowerShell --source winget. Do not run the install without confirmation.
3. Resolve the AL toolchain
powershell -NoProfile -ExecutionPolicy Bypass -File <plugin>/skills/bc-bootstrap/scripts/resolve-al-tools.ps1
Parse the JSON output.
status: "ok"→ note thetoolsPathand proceed to step 5.status: "not-found"→ proceed to step 4 (download from marketplace).
4. Download the AL vsix (fallback)
Ask the user: "The AL toolchain was not found on this machine. Download the AL Language extension from the Visual Studio Marketplace into the plugin's cache? This is a one-time download of ~100 MB." Only proceed on confirmation.
powershell -NoProfile -ExecutionPolicy Bypass -File <plugin>/skills/bc-bootstrap/scripts/download-al-vsix.ps1
If the result is status: "error", surface the message to the user and stop.
5. Offer to install BcContainerHelper if missing
powershell -NoProfile -Command "if (Get-Module -ListAvailable BcContainerHelper) { 'installed' } else { 'missing' }"
If the output is missing, tell the user: "BcContainerHelper is required for container mode (debug/test workflows). It is not needed for compile-only work. Install now? (Install-Module BcContainerHelper -Scope CurrentUser -Force)" Only install on confirmation. Do not fail bootstrap if the user declines — container mode will fail later if attempted.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 88 lines · 64 tokens per session scan A 0093f0d8237d
bc-bootstrap is a skill published in the GitHub repository loacher-solution/bc-agent-plugin (2 stars, last pushed 4mo ago), licensed MIT. It adds 64 tokens to every session and 1,049 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…