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/commands/arenadata/adcm-agent/adcm-teardown)<a href="https://agentmods.dev/commands/arenadata/adcm-agent/adcm-teardown"><img src="https://agentmods.dev/badge/commands/arenadata/adcm-agent/adcm-teardown.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.00014 | $0.00360 |
| Opus 5 | $0.00007 | $0.00180 |
| Sonnet 5 | $0.00003 | $0.00072 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
adcm-teardown 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 7d 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
Clean up after test deploys. Target: $ARGUMENTS
Show what is yours first, and confirm
ADCM="python3 ${CLAUDE_PLUGIN_ROOT}/scripts/adcmctl.py"
$ADCM owned # clusters and bundles this checkout created on this instance
$ADCM clusters # everything on the instance, for context
owned reads the ownership records in <repo>/.adcm/state.json. Anything not in that list
belongs to somebody else.
Deletion is destructive and not reversible. List what you are about to remove and get confirmation before removing it, even when the user asked for a teardown — they may not know a cluster on that list is still in use.
Then remove, cluster before bundle
$ADCM delete-cluster <clusterId>
$ADCM delete-bundle <bundleId>
Order matters: ADCM refuses to delete a bundle a cluster is using.
Both commands refuse anything this checkout did not create. If one refuses, that is the
guard working — do not reach for --force. Use it only when the object's owner has
explicitly said yes, and say in your report that you did.
Hosts
Deleting a cluster releases its hosts back to the free pool. Do not delete hosts or hostproviders; they belong to the instance owner.
Report
What you removed, by id and name; what you deliberately left and why; and anything the guard refused, so the user can take it up with the owner.
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.
- 7d ago First seen · 45 lines · 14 tokens per session scan A 5c07e93e6d33
adcm-teardown is a command published in the GitHub repository arenadata/adcm-agent (2 stars, last pushed 14d ago), licensed Apache-2.0. It adds 14 tokens to every session and 360 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
cost-optimize
You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, GCP, and OCI. Where provider-specific code appears below, adapt…
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
integrate
Set up third-party service integrations.
env
Manage Vercel environment variables. Commands include list, pull, add, remove, and diff. Use to sync environment variables between Vercel and your local development environment.
scan
Scan AWS account for cost optimization.
finops-feedback
Step 5 (Feedback Loop & Celebration) — measure realized against projected savings, compute a labelled Cloud Entropy proxy, close the opportunity, and emit at least one new idea or policy update so the loop actually closes. Applies the double-loop gate. Mutates on the closure path.