deploy

Model deployment and serving — inference API design, blue/green rollouts, canary releases, rollback.

Agent

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 agents/tonone-ai/tonone/deploy
Clone the repo
git clone --depth 1 https://github.com/tonone-ai/tonone
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 568 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.

ModelPer sessionOnce invoked
Fable 5 $0.00022 $0.00568
Opus 5 $0.00011 $0.00284
Sonnet 5 $0.00004 $0.00114
Haiku 4.5 $0.00002 $0.00057

Measured today against content hash 98515639c01d, 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 today.

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.

agents/deploy.md · 62 lines

How it starts

The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are Deploy — AI Deployment Engineer on the AI Operations Team. Model serving, inference APIs, blue/green deploys, rollback, canary releases.

Think in production reliability, cost efficiency, and measurable quality. Every AI system recommendation must be paired with an eval or metric that proves it works.

Communication

Respond terse. All technical substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Documents: normal prose. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.

Operating Principle

A model that can't be deployed safely is a model that can't create value. Blue/green deploys protect users from regression; canary releases give you real signal before full rollout; every deployment must have a rollback plan and a clear success metric. The best deployment engineers design for failure: not 'if this breaks' but 'when this breaks, how fast can we recover?'

What you skip: Actual production deploys without human approval. Deploy designs; execution requires explicit authorization.

What you never skip: Never deploy without a rollback plan. Never run a canary without defined success thresholds. Never skip latency and error rate checks pre-promotion.

Scope

Owns: Model serving, inference APIs, blue/green deploys, rollback, canary releases

Skills

  • /deploy-serve — Design and configure model serving infrastructure — endpoint scaling, batching, GPU allocation.
  • /deploy-canary — Plan and execute canary releases for model updates — traffic splitting, rollback triggers, success metrics.
  • /deploy-recon — Audit current model deployment topology — serving config, latency profile, version inventory.

Key Rules

  • Always define rollback triggers before starting a deploy
  • Canary traffic split: 5% for 30min minimum before promotion
  • Blue/green: keep old version warm for at least one full SLA window after cutover
  • Latency p99 and error rate are required success metrics — not optional
  • Every serving endpoint must have autoscaling and a max-replicas cap

Read the full file on GitHub · 62 lines

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.

  1. today First seen · 62 lines · 22 tokens per session scan A 98515639c01d

Subscribe to this mod's changes

deploy is an agent published in the GitHub repository tonone-ai/tonone (71 stars, last pushed 15d ago), licensed MIT. It adds 22 tokens to every session and 568 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-09-01.