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 commands/arenadata/adcm-agent/adcm-deploygit clone --depth 1 https://github.com/arenadata/adcm-agentWhat 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.00013 | $0.00716 |
| Opus 5 | $0.00006 | $0.00358 |
| Sonnet 5 | $0.00003 | $0.00143 |
| Haiku 4.5 | $0.00001 | $0.00072 |
Grade A, and why
adcm-deploy 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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy a cluster on the configured ADCM instance. Target: $ARGUMENTS
Load the adcm-cluster-deploy skill — it owns the sequence, the concern workflow and the attribution table. For a long or unattended run, delegate to the adcm-deploy-operator agent instead of driving it inline.
Establish three things before touching the instance
State each one in your first message:
- Which instance —
adcmctl.py whoami. Unconfigured means/adcm-connectfirst. - Which hosts you may use —
deploy.hostsfrom the config, the user's answer, or--count Nagainsthosts --freewith the selection reported. Never take a host that belongs to another cluster; never assume a host name. - Which bundle — a fresh build, or something already uploaded (
bundles --mine).
If any is unresolved, ask. A deploy against the wrong instance is not recoverable.
Then run the sequence
ADCM="python3 ${CLAUDE_PLUGIN_ROOT}/scripts/adcmctl.py"
$ADCM upload # if you built something
$ADCM prototype --type cluster # id + licence status
$ADCM accept-license <prototypeId> # only when unaccepted
$ADCM create-cluster --prototype-id <id>
$ADCM add-services --cluster <clusterId>
$ADCM add-hosts --cluster <clusterId> --names <hosts>
$ADCM map --cluster <clusterId>
$ADCM concerns --cluster <clusterId> # work this list until it is empty
$ADCM run-action --cluster <clusterId> --name install --wait
Two things you own beyond the commands:
Concerns are authoritative. required-configs misses fields that are invalid rather
than absent. When a concern is not specific enough, re-post the service's configuration
unchanged (set-config with no --set) and read the validation error.
Never put a secret in a command line. --gen-secret KEY --show-generated or
--set-env KEY=ENV_VAR. Credentials you generate exist nowhere else — they must be in your
report.
Install takes tens of minutes. Run it in a background shell and poll; do not block one call
on the whole task, and do not re-run one that timed out — wait-task <id> re-attaches.
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 · 67 lines · 13 tokens per session scan A effde91f12b0
adcm-deploy is a command published in the GitHub repository arenadata/adcm-agent (2 stars, last pushed 9d ago), licensed Apache-2.0. It adds 13 tokens to every session and 716 once invoked, about $0.0001 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 commands, from other repositories
account
This API allows you to manage your Scaleway Projects.
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
deploy
Build, test, deploy with staged rollout.
d1-migration
Run D1 migration workflow — generate, inspect, apply.
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
deploy
Build a container image, push it, and deploy the service to the Akka platform. This is the transition from local development to development on the AAO platform.