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.
npx agentmods add commands/felipeslo/opencode-kit/deploygit clone --depth 1 https://github.com/felipeslo/opencode-kitWhat 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 | $0.00013 | $0.00826 |
| Opus 5 | $0.00006 | $0.00413 |
| Sonnet 5 | $0.00003 | $0.00165 |
| Haiku 4.5 | $0.00001 | $0.00083 |
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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/deploy - Production Deployment
$ARGUMENTS
Purpose
This command handles production deployment with pre-flight checks, deployment execution, and verification.
Sub-commands
/deploy - Interactive deployment wizard
/deploy check - Run pre-deployment checks only
/deploy preview - Deploy to preview/staging
/deploy production - Deploy to production
/deploy rollback - Rollback to previous version
Pre-Deployment Checklist
Before any deployment:
## 🚀 Pre-Deploy Checklist
### Code Quality
- [ ] No TypeScript errors (`npx tsc --noEmit`)
- [ ] ESLint passing (`npx eslint .`)
- [ ] All tests passing (`npm test`)
### Security
- [ ] No hardcoded secrets
- [ ] Environment variables documented
- [ ] Dependencies audited (`npm audit`)
### Performance
- [ ] Bundle size acceptable
- [ ] No console.log statements
- [ ] Images optimized
### Documentation
- [ ] README updated
- [ ] CHANGELOG updated
- [ ] API docs current
### Ready to deploy? (y/n)
Deployment Flow
┌─────────────────┐
│ /deploy │
└────────┬────────┘
│
▼
┌─────────────────┐
│ Pre-flight │
│ checks │
└────────┬────────┘
│
Pass? ──No──► Fix issues
│
Yes
│
▼
┌─────────────────┐
│ Build │
│ application │
└────────┬────────┘
│
▼
┌─────────────────┐
│ Deploy to │
│ platform │
└────────┬────────┘
│
▼
┌─────────────────┐
│ Health check │
│ & verify │
└────────┬────────┘
│
▼
┌─────────────────┐
│ ✅ Complete │
└─────────────────┘
Output Format
Successful Deploy
## 🚀 Deployment Complete
### Summary
- **Version:** v1.2.3
- **Environment:** production
- **Duration:** 47 seconds
- **Platform:** Vercel
### URLs
- 🌐 Production: https://app.example.com
- 📊 Dashboard: https://vercel.com/project
### What Changed
- Added user profile feature
- Fixed login bug
- Updated dependencies
### Health Check
✅ API responding (200 OK)
✅ Database connected
✅ All services healthy
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.
- yesterday First seen · 177 lines · 13 tokens per session scan A d295b9167932
deploy is a command published in the GitHub repository felipeslo/opencode-kit (2 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 826 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-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.