deploy

A deployment procedure for moving an application to a server or production environment. It checks the project, creates a backup, deploys using the usual method, and verifies that the service works.

In plain words
What is it for?
Use it when deploying, pushing to production, or shipping a release, including pre-release checks, backups, health checks, log checks, smoke tests, and rollback planning.
Why use it?
It reduces the risk of taking an application offline or losing the previous version during a release.

Skill for Claude CodeCodex

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 skills/ozmasterai/torus-framework/deploy
Any agent
npx skills add OZmasterAI/Torus-Framework --skill deploy
Clone the repo
git clone --depth 1 https://github.com/OZmasterAI/Torus-Framework

Made for: Claude Code, Codex.

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 347 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00000 $0.00347
Opus 5 $0.00000 $0.00173
Sonnet 5 $0.00000 $0.00069
Haiku 4.5 $0.00000 $0.00035

Measured yesterday against content hash d8e9ba9f8a84, 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 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 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- Run a smoke test (curl endpoint, check response)
dormant/skills/standalone/deploy/SKILL.md · 32 lines

What it actually says

/deploy — Safe Deployment with Backup and Verification

When to use

When the user says "deploy", "push to prod", "ship it", or wants to deploy to a server.

Steps

  1. PRE-FLIGHT CHECKS:
    • search_knowledge("deploy issues production") for known deployment problems
    • Run full test suite — Gate 3 enforces this but do it explicitly
    • Check git status — ensure working tree is clean
    • Verify the target environment is reachable
  2. BACKUP (if deploying to server):
    • SSH to server and create a timestamped backup of current deployment
    • Example: ssh server 'cp -r /opt/app /opt/app.backup.$(date +%Y%m%d_%H%M%S)'
    • Save backup location to memory
  3. DEPLOY:
    • Use the project's standard deployment method
    • For direct deploys: scp/rsync files to server
    • For container deploys: docker push + pull
    • For git deploys: git push to deployment remote
  4. VERIFY:
    • Health check the deployed service
    • Check logs for errors: journalctl -u service -n 50
    • Run a smoke test (curl endpoint, check response)
  5. ROLLBACK PLAN:
    • If verification fails, restore from backup immediately
    • Save the failure details to memory
  6. POST-DEPLOY:
    • remember_this() with deployment details, version, and timestamp
    • Update LIVE_STATE.json with deployment info
    • Update LIVE_STATE.json
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. yesterday First seen · 32 lines · 0 tokens per session scan A d8e9ba9f8a84

Subscribe to this mod's changes

deploy is a skill published in the GitHub repository OZmasterAI/Torus-Framework (5 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 347 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens