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.
git clone --depth 1 https://github.com/oxygen-fragment/claude-modularWrote 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/oxygen-fragment/claude-modular/deploy-staging)<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/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/oxygen-fragment/claude-modular/deploy-staging"><img src="https://agentmods.dev/badge/commands/oxygen-fragment/claude-modular/deploy-staging.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.00000 | $0.00582 |
| Opus 5.5 | $0.00000 | $0.00233 |
| Sonnet 5.5 | $0.00000 | $0.00116 |
| Haiku 4.5 | $0.00000 | $0.00058 |
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 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.
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.
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
```
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 · 98 lines · 0 tokens per session scan A de8e38ccc6ec
deploy-staging is a command published in the GitHub repository oxygen-fragment/claude-modular (285 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.
Other commands, from other repositories
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
paul:help
Show available PAUL commands and usage guide.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
mutate
Run mutation testing to verify test quality. Builds a custom mutation tool or uses an existing framework, runs mutations, and reports the mutation score with surviving mutants.
deep-audit.skeleton
Description: This section is populated by Bootstrap with manifest data. Required manifest fields: project.description, stack.primary, project.structure, project.subprojects, stack.orm, stack.authmethod Example output.
architect
Generate architecture.md with system design decisions from foundation documents.