Borrowing it
Nothing to install: this file belongs to terrene-foundation/metis. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/terrene-foundation/metis/main/.claude/commands/deploy.mdgit clone --depth 1 https://github.com/terrene-foundation/metisWrote 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/terrene-foundation/metis/deploy)<a href="https://agentmods.dev/commands/terrene-foundation/metis/deploy"><img src="https://agentmods.dev/badge/commands/terrene-foundation/metis/deploy/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/terrene-foundation/metis/deploy"><img src="https://agentmods.dev/badge/commands/terrene-foundation/metis/deploy.svg" alt="Reviewed on agentmods" width="80" 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.00023 | $0.01949 |
| Opus 5.5 | $0.00009 | $0.00780 |
| Sonnet 5.5 | $0.00005 | $0.00390 |
| Haiku 4.5 | $0.00002 | $0.00195 |
Grade A, and why
deploy scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
LIVE_HTML=$(curl -fsSL -H "Cache-Control: no-cache" -H "Pragma: no-cache" "$LIVE_URL") This is a copy
89% identical to deploy — 46 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/deploy - Application Deployment
For applications that ship code to running environments (containers, edge functions, VMs, k8s, mobile stores). Driven by deploy/deployment-config.md.
NOT to be confused with /release — /release publishes packages to artifact registries (PyPI, crates.io, npm). /deploy ships running code. If your repo's deploy/deployment-config.md declares type: sdk, this command redirects to /release.
Mode Detection
/deploy → Execute mode
/deploy --check → Check mode (drift detection only, no deploy)
/deploy --onboard → Onboard mode (create deployment-config.md)
If deploy/deployment-config.md does NOT exist → Onboard Mode
Run the application deployment onboarding process. See skills/10-deployment-git/application-deployment.md.
- Detect platform — read repo for clues:
Dockerfile,vercel.json,fly.toml,app.yaml,kubernetes/,azure-pipelines.yml,containerapps/,Procfile, native binaries - Ask the human — what platform, what deploy command, what counts as "production code", how to query current deployed state, staging required?
- Research current best practices — web search for platform-specific deploy patterns (Container Apps revisions, Fly machines, Cloud Run revisions, etc.). Do NOT rely on encoded knowledge — cloud platform CLIs change frequently.
- Create
deploy/deployment-config.md— see schema inskills/10-deployment-git/application-deployment.md - STOP — present to human for review
If deploy/deployment-config.md declares type: sdk → Redirect
This repo is an SDK. Run /release instead — it handles version bumping, PyPI/registry publishing, and artifact validation.
If deploy/deployment-config.md declares type: application → Execute Mode
Read the config and execute. Print the 10-step DEPLOY CHECKLIST at the start of the response and check off boxes as each step passes. Do NOT report deploy as complete until every box is checked. The full checklist text and per-step guidance lives in rules/deploy-hygiene.md Rule 8 and skills/10-deployment-git/application-deployment.md. If any step fails, say "DEPLOY FAILED AT STEP N: " — NOT "build succeeded, will redeploy soon".
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.
- 1mo ago First seen · 136 lines · 23 tokens per session scan A 0759d4b25139
deploy is a command published in the GitHub repository terrene-foundation/metis (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 1,949 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 89% identical to deploy, differing in 46 lines, and is treated as a copy.
Other commands, from other repositories
dart-fix-ci
Command "dart-fix-ci" from dartsim/dart, covering required reading, workflow and output.
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
access
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
check-release-health
Summarize the CI health of an OpenShift release using live data from the openshift-ci-mcp server.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
analyst
Use when performing local analyst review before pushing PR changes. Assesses code quality, impact analysis, and maintainability.