deploy-staging

deploy-staging is a command for Claude Code from oxygen-fragment/claude-modular. It costs 0 tokens per session (582 once invoked), scanned A, original, MIT.

A command for deploying a software version to a staging environment, which is a test setup kept separate from the live application.

In plain words
What is it for?
Use it to deploy a chosen version, run health checks and smoke tests, verify integrations, configure monitoring, and produce a deployment report.
Why use it?
It provides a place to check deployment health and key user journeys before releasing changes to production.

Command for Claude Code

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/oxygen-fragment/claude-modular/deploy-staging
Clone the repo
git clone --depth 1 https://github.com/oxygen-fragment/claude-modular

Made for: Claude Code.

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

agentmods badge for deploy-staging

README.md
[![agentmods](https://agentmods.dev/badge/commands/oxygen-fragment/claude-modular/deploy-staging.svg)](https://agentmods.dev/commands/oxygen-fragment/claude-modular/deploy-staging)
Your own site
<a href="https://agentmods.dev/commands/oxygen-fragment/claude-modular/deploy-staging"><img src="https://agentmods.dev/badge/commands/oxygen-fragment/claude-modular/deploy-staging.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 582 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.1 $0.00000 $0.00582
Opus 5 $0.00000 $0.00291
Sonnet 5 $0.00000 $0.00116
Haiku 4.5 $0.00000 $0.00058

Measured 5d ago against content hash de8e38ccc6ec, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

deploy-staging 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 5d 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.

.claude/commands/deployment/deploy-staging.md · 98 lines

What it actually says

Deploy Staging Command

2. **Deployment Execution**
   - Execute deployment pipeline
   - Monitor deployment progress
   - Handle deployment failures gracefully
   - Maintain deployment logs and audit trail

3. **Service Validation**
   - Verify service startup and health checks
   - Test API endpoints and functionality
   - Validate database connections and migrations
   - Check external service integrations

4. **Smoke Testing**
   - Execute critical user journeys
   - Validate key business functionality
   - Test authentication and authorization
   - Verify performance characteristics

5. **Monitoring Setup**
   - Configure environment-specific monitoring
   - Set up alerting for staging issues
   - Enable logging and tracing
   - Create deployment dashboards

6. **Validation and Sign-off**
   - Generate deployment report
   - Document any issues or concerns
   - Collect stakeholder approval
   - Prepare production deployment plan
# Deployment process:
# - Environment validation
# - Artifact deployment
# - Service health checks
# - Smoke test execution
```

```bash
# Deploy specific version to staging
/deploy:deploy-staging --version=1.2.3

# Version-specific deployment:
# - Tagged release deployment
# - Version validation
# - Rollback planning
# - Change documentation
```

```bash
# Deploy with custom configuration
/deploy:deploy-staging --config=feature-flags-enabled

# Custom deployment:
# - Feature flag configuration
# - A/B testing setup
# - Experimental features
# - Controlled rollout
```
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. 5d ago First seen · 98 lines · 0 tokens per session scan A de8e38ccc6ec

Subscribe to this mod's changes

deploy-staging is a command published in the GitHub repository oxygen-fragment/claude-modular (283 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 582 tokens. 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-30.