A command that checks whether the current app is ready for deployment and reports existing deployment details. Creating a new production deployment is currently unavailable.

Use it to run deployment readiness checks, inspect existing deployment status or logs, and retrieve an existing app URL.

It shows authentication, preflight checks, and the current deployment limitation before anything is uploaded or published.

deploy — Command by StructureIntelligence

Install

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.

agentmods

npx agentmods add commands/structureintelligence/semesh/deploy

Clone the repo

git clone --depth 1 https://github.com/StructureIntelligence/Semesh

Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 550 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00016	$0.00550
Opus 5	$0.00008	$0.00275
Sonnet 5	$0.00003	$0.00110
Haiku 4.5	$0.00002	$0.00055

Measured yesterday against content hash 04d7671c3531, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 yesterday.

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.

commands/deploy.md · 24 lines

What it actually says

Prepare the app in the current directory, report the current deployment availability truth, and observe existing deployment records when ids are provided.

Steps:

Confirm auth: run semesh whoami --json. If it returns 401, tell the user to run semesh login (or set SEMESH_API_KEY) and stop — never proceed past a 401.
Read the mutation tool before packaging anything:
```
semesh tool show app_deployments.create --json
```
Inspect the project shape and run the authenticated, read-only preflight:
```
semesh deploy preflight . --full-stack --json
```
Read tool availability plus preflight admission.can_start_now, code, message, and fix. Production deployment authorization is currently unavailable: app_deployments.create is disabled and deploy fails closed with deployment_authorization_unavailable before upload, build, payment, publication, or a live URL. Report that result and stop without a mutation.
For ids that already exist, use semesh deploy status <app-id> --json, semesh deploy logs <build-id> --json, and semesh deploy url <app-id> --json. Existing observation does not authorize a new release, and queued/candidate/preview state is not serving proof.
When deployment authorization becomes available and both checks allow the operation, the intended full-stack command is semesh deploy . --name "$(basename "$PWD")" --full-stack --wait --json (drop --full-stack for a plain static site). Report a live URL only from a successful serving response or URL readback; never construct one.
If the user wants an already serving app to charge end users, explain end-user-pays: the app attaches X-Semesh-Payer so each call is billed to the signed-in user's Aev balance, with a quote before spend and terminal capture evidence afterward.

A direct user request authorizes ordinary paid invocation, deploy, and mechanical publish without a duplicate confirmation. Quote/preflight informs cost and availability; it is not a second confirmation. Ask for a separate confirmation only for destructive, high-impact, authorization-expanding, truly irreversible, or explicitly requires_confirmation actions. Mechanical protocol checks are intended to publish automatically after authorization is available; there is no default human approval queue. If an already-started deployment's --wait times out, poll semesh deploy status <app-id> --json rather than concluding failure.

Changes

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.

yesterday First seen · 24 lines · 16 tokens per session scan A 04d7671c3531

Subscribe to this mod's changes

deploy is a command published in the GitHub repository StructureIntelligence/Semesh (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 16 tokens to every session and 550 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.

DevOps and cloud ai-agents billing claude-code cursor deploy mcp

deploy

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

migrate

cost-tracker

lians-recall

t800-onboard

dev-planner

generate-role