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 skills add escapeboy/ai-prompts --skill example-complexgit clone --depth 1 https://github.com/escapeboy/ai-promptsWrote 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/skills/escapeboy/ai-prompts/example-complex)<a href="https://agentmods.dev/skills/escapeboy/ai-prompts/example-complex"><img src="https://agentmods.dev/badge/skills/escapeboy/ai-prompts/example-complex/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/skills/escapeboy/ai-prompts/example-complex"><img src="https://agentmods.dev/badge/skills/escapeboy/ai-prompts/example-complex.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.00009 | $0.02888 |
| Opus 5.5 | $0.00004 | $0.01155 |
| Sonnet 5.5 | $0.00002 | $0.00578 |
| Haiku 4.5 | $0.00001 | $0.00289 |
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 21d 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.
How it starts
The opening of the file, as written. The whole thing — 569 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy
Complete deployment workflow for staging and production environments. Includes pre-flight checks, build steps, deployment, and post-deployment verification.
Usage
/deploy [environment] [options]
Quick Examples
/deploy # Deploy to staging (default)
/deploy staging # Explicit staging deploy
/deploy production # Deploy to production
/deploy production --force # Skip confirmations
/deploy --dry-run # Preview deployment steps
Actions
1. Deploy to Staging (Default)
When invoked without arguments or with staging, deploys to staging environment.
Usage:
/deploy
/deploy staging
Process:
Step 1: Pre-Flight Checks
- Verify on correct branch (main or release/*)
- Check for uncommitted changes
- Verify all tests pass
- Check build succeeds
Step 2: Prepare Deployment
- Create deployment tag:
staging-YYYYMMDD-HHMMSS - Update version in application files
- Generate changelog since last deployment
Step 3: Build
- Run production build:
npm run build(frontend)composer install --no-dev(backend)
- Optimize assets
- Clear and rebuild caches
Step 4: Deploy
- SSH to staging server
- Pull latest code
- Run migrations
- Clear application caches
- Restart workers/services
Step 5: Verify
- Run smoke tests against staging
- Check application health endpoint
- Verify key features work
Example Output:
🚀 Deploying to STAGING
Pre-flight checks:
✅ On branch: main
✅ No uncommitted changes
✅ Tests pass (42 passed)
✅ Build succeeds
Preparing deployment:
✅ Created tag: staging-20260104-143022
✅ Updated version: 1.5.3
Building:
✅ Frontend built (32s)
✅ Backend optimized (8s)
Deploying:
✅ Connected to staging.example.com
✅ Code pulled
✅ Migrations run (3 new)
✅ Caches cleared
✅ Workers restarted
Verification:
✅ Health check passed
✅ Smoke tests passed (5/5)
🎉 Deployment complete!
URL: https://staging.example.com
Version: 1.5.3
Duration: 2m 34s
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.
- 21d ago First seen · 569 lines · 9 tokens per session scan A deb281f82064
deploy is a skill published in the GitHub repository escapeboy/ai-prompts (91 stars, last pushed 9d ago), licensed MIT. It adds 9 tokens to every session and 2,888 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-25.
Other skills, from other repositories
render
Use when deploying or fixing an app on Render — web services, background workers, cron jobs, private services, managed Postgres and Key-Value, and especially the render.yaml Blueprint. Covers deploys that fail with no open ports detected, 502s on first deploy, free-tier cold starts, and a free Postgres about to expire…
cloud-deploy-gcp-aws
Use when a backend or worker service needs a cloud deploy - container-first GitHub Actions deploys to Google Cloud Run (WIF) or AWS ECS/App Runner (OIDC), with migrate-before-deploy and a health-check gate.
deployment
Deploy applications to DigitalOcean App Platform via GitHub Actions with proper environment management and secrets handling. Use when setting up CI/CD pipelines, configuring staging/production environments, managing deployment secrets, or creating GitHub Actions workflows.
blockchain-infrastructure
Use this skill when asked about blockchain node deployment, RPC infrastructure, CI/CD for smart contracts, monitoring and alerting for blockchain networks, MEV infrastructure (Flashbots, builders, relays), key management (KMS, HSM), and environment management for devnet/testnet/staging/mainnet. Languages: Go, Rust…
devops-specialist
DevOps agent specializing in deployment, monitoring, and infrastructure automation.
deploio-manage
Day-to-day operations on a running Deploio app — config changes, routine log monitoring, console/exec access, and redeployments. This skill should be triggered for: "change env vars", "scale app", "add worker", "cron job", "scheduled job", "custom domain", "retry build", "deploy new version", "tail logs", "show me the…