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/rcdelacruz/claude-code-agents/workflow-deploygit clone --depth 1 https://github.com/rcdelacruz/claude-code-agentsWhat 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.00008 | $0.02900 |
| Opus 5 | $0.00004 | $0.01450 |
| Sonnet 5 | $0.00002 | $0.00580 |
| Haiku 4.5 | $0.00001 | $0.00290 |
Grade A, and why
workflow-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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl https://your-app.com/api/health How it starts
The opening of the file, as written. The whole thing — 541 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are in DEPLOYMENT MODE.
Use deployment agent to set up production deployment and CI/CD.
Deployment Workflow
1. Pre-Deployment Checklist (10 mins)
Code Quality
- All tests passing
- Code reviewed and approved
- No console.logs or debugging code
- No TODOs for critical features
- TypeScript builds without errors
Security
- Environment variables configured
- Secrets not in code
- API keys rotated for production
- Security audit passed
- Dependencies updated (npm audit)
Performance
- Bundle size optimized
- Images optimized
- Core Web Vitals targets met
- Database indexes added
Configuration
- Production environment variables set
- Database connection configured
- CDN configured
- Domain/DNS configured
- SSL certificate configured
2. Database Migration (15 mins)
Prepare Migration
# Review pending migrations
npx prisma migrate status
# Create migration if needed
npx prisma migrate dev --name deployment_prep
# Generate Prisma Client
npx prisma generate
Production Migration Strategy
# Option 1: Run migration during deployment (small changes)
npx prisma migrate deploy
# Option 2: Run migration separately (breaking changes)
# 1. Add new columns (nullable)
# 2. Deploy code that works with both old/new schema
# 3. Backfill data
# 4. Deploy code that requires new schema
# 5. Remove old columns
Migration Checklist
- Migrations tested in staging
- Backup database before migration
- Migration is backwards compatible (if zero-downtime)
- Rollback plan documented
- Data migration scripts tested
3. Vercel Deployment (Recommended) (10 mins)
Setup Vercel
# Install Vercel CLI
npm install -g vercel
# Login
vercel login
# Link project
vercel link
Configure Environment Variables
# Add via CLI
vercel env add DATABASE_URL production
vercel env add NEXTAUTH_SECRET production
vercel env add NEXTAUTH_URL production
# Or via dashboard: vercel.com/[team]/[project]/settings/environment-variables
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.
- 2d ago First seen · 541 lines · 8 tokens per session scan A 4e07c1735aff
workflow-deploy is a command published in the GitHub repository rcdelacruz/claude-code-agents (2 stars, last pushed 10mo ago), licensed MIT. It adds 8 tokens to every session and 2,900 once invoked, about $0.0000 per session on Opus 5. 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.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.