Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add arenadata/adcm-agent/plugin install adcmWrote 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/arenadata/adcm-agent/adcm-bundle-build)<a href="https://agentmods.dev/skills/arenadata/adcm-agent/adcm-bundle-build"><img src="https://agentmods.dev/badge/skills/arenadata/adcm-agent/adcm-bundle-build.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.1 | $0.00124 | $0.02045 |
| Opus 5 | $0.00062 | $0.01022 |
| Sonnet 5 | $0.00025 | $0.00409 |
| Haiku 4.5 | $0.00012 | $0.00204 |
Grade A, and why
adcm-bundle-build 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 5d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Building an ADCM bundle locally
These repositories carry no build tooling of their own — CI packs them with a shared
pipeline template. bundle_build.py reimplements that packer from the repository's own
spec.yaml, so it works on any bundle repo without being told anything about the product.
One-time setup, then the loop
ADCM_SCRIPTS="${CLAUDE_PLUGIN_ROOT}/scripts"
bash "$ADCM_SCRIPTS/bootstrap.sh" # provisions <repo>/.adcm/venv, idempotent
PY=.adcm/venv/bin/python
Run the render check after every edit to a .j2 the splitter owns. It takes about a
second and it is the compile check for a bundle refactor:
$PY "$ADCM_SCRIPTS/bundle_build.py" --check
Then, when you want an artifact:
$PY "$ADCM_SCRIPTS/bundle_build.py" --dev-version --skip-pymod # iteration
$PY "$ADCM_SCRIPTS/bundle_build.py" # faithful build
Output lands in <repo>/.adcm/dist/, the exact tree that was packed stays in
<repo>/.adcm/staging/<edition>/, and <repo>/.adcm/state.json records the build so
adcmctl.py upload needs no arguments.
Options
| Flag | Meaning |
|---|---|
--edition NAME |
edition from spec.yaml; default enterprise, else the first declared |
--check |
render and validate only, no archive |
--dev-version |
append _dev_<epoch> to the top prototype's version |
--version-suffix S |
an explicit suffix instead |
--release |
render with release_version=true (production package repositories) |
--context K=V |
extra Jinja context for the splitter templates, repeatable |
--skip-pymod |
skip python_mod_req wheel vendoring |
--pymod-target DIR |
where inside the archive the wheels go; default the bundle root |
--stub-submodules |
render with empty stubs for unfetched submodules; --check only |
--no-submodule-update |
do not run git submodule update |
--repo PATH |
build a repository other than the one containing the working directory |
What ships with it
1 file 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.
- 5d ago First seen · 149 lines · 124 tokens per session scan A 7af1e15aaa8e
adcm-bundle-build is a skill published in the GitHub repository arenadata/adcm-agent (2 stars, last pushed 12d ago), licensed Apache-2.0. It adds 124 tokens to every session and 2,045 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…