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/rohittcodes/claude-plugin-suiteWrote 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/rohittcodes/claude-plugin-suite/deploy)<a href="https://agentmods.dev/commands/rohittcodes/claude-plugin-suite/deploy"><img src="https://agentmods.dev/badge/commands/rohittcodes/claude-plugin-suite/deploy/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/rohittcodes/claude-plugin-suite/deploy"><img src="https://agentmods.dev/badge/commands/rohittcodes/claude-plugin-suite/deploy.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.00007 | $0.00296 |
| Opus 5.5 | $0.00003 | $0.00118 |
| Sonnet 5 | $0.00001 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00030 |
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 7d 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
Deployment Command
Deploy the application to the specified environment with comprehensive validation.
Context
- Environment: $1 (default: production)
- Service: $2 (default: current service)
- Current branch: !
git branch --show-current - Recent commits: !
git log --oneline -5 - Build status: !
git status --porcelain
Deployment Process
-
Pre-deployment Checks
- Validate environment configuration
- Check service dependencies
- Verify security requirements
- Confirm deployment permissions
-
Build and Test
- Run automated tests
- Perform security scans
- Validate configuration
- Build deployment artifacts
-
Deployment Execution
- Deploy to target environment
- Verify service health
- Run smoke tests
- Monitor deployment metrics
-
Post-deployment Validation
- Health check validation
- Performance monitoring
- Error log analysis
- User acceptance testing
Expected Outcome
- Successful deployment to $1 environment
- All health checks passing
- Performance metrics within acceptable ranges
- Zero critical errors in logs
Rollback Plan
If deployment fails:
- Automatic rollback to previous version
- Restore database state if needed
- Notify stakeholders of issues
- Document failure reasons for analysis
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.
- 7d ago First seen · 55 lines · 0 tokens per session scan A f8c1a91a7440
deploy is a command published in the GitHub repository rohittcodes/claude-plugin-suite (29 stars, last pushed 11mo ago), licensed MIT. It adds 7 tokens to every session and 296 once invoked, about $0.0000 per session on Opus 5.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-21.
Other commands, from other repositories
ci-setup
Setup CI pipeline from scratch. Creates GitHub Actions or GitLab CI configuration with lint, test, build, and deploy stages.
write-test-plan
Generate or update change test plan.
harness:cicd-fleet
Autonomous CI/CD-remediation orchestrator — triage the red CI/CD-run and flaky-test backlog by cause, fan out worktree-isolated subagents that run the real deflake/heal pipeline, independently verify each fix by artifact and deterministic all-OS CI, and hand back a batch of remediation PRs for one bulk human review.…
quality-check
Execute a comprehensive quality gate check (lint, test, build, format) before allowing code to merge.
check-fix
Execute quality gates, fix any issues found, and create a single high-quality Conventional Commit summarizing all changes made.
ship
Before merging or deploying, run ALL of the following checks. Every gate must pass.