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 skills/mracal/vibe-engineering/safe-deploynpx skills add mracal/vibe-engineering --skill safe-deploygit clone --depth 1 https://github.com/mracal/vibe-engineeringWrote 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/mracal/vibe-engineering/safe-deploy)<a href="https://agentmods.dev/skills/mracal/vibe-engineering/safe-deploy"><img src="https://agentmods.dev/badge/skills/mracal/vibe-engineering/safe-deploy.svg" alt="Measured on agentmods" 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 | $0.00035 | $0.00554 |
| Opus 5 | $0.00017 | $0.00277 |
| Sonnet 5 | $0.00007 | $0.00111 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
vibe-safe-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 5d 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.
This is a copy
100% identical to vibe-safe-deploy — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
vibe-safe-deploy
Ship with confidence. Every deployment should be verifiable and reversible.
When to Use This Skill
- Deploying to staging or production environments
- Releasing a new version
- Deploying infrastructure changes
When NOT to Use This Skill
- Local development builds
- CI/CD that already handles these checks
- Deploying documentation (low risk)
Pre-Flight Checklist
Before deploying, verify:
- All tests pass (including integration tests)
- Linting is clean
- No uncommitted changes in working tree
- No secrets in the diff (
grep -r 'API_KEY\|SECRET\|PASSWORD') - Build succeeds
- Database migrations are reversible (if applicable)
Steps
-
Pre-flight checks — Run all items in checklist. Stop if any fail.
-
Backup current state:
cp -r current_deploy/ current_deploy.prev/ # or: docker tag app:current app:rollback -
Deploy using atomic operations:
# Use 'install' not 'cp' for atomic file replacement install -m 755 new_binary /path/to/binary # or: docker tag app:new app:current && docker-compose up -d -
Health check (within 60s timeout):
- Service starts successfully
- Health endpoint returns 200
- Key functionality works (smoke test)
- No error spikes in logs
-
If health check fails → automatic rollback:
cp -r current_deploy.prev/ current_deploy/ # Restart services with previous version -
Report status: success / failed / rolled-back
Output Format
Deployment Report
Status: SUCCESS / FAILED / ROLLED_BACK Version: [version or commit hash] Duration: [time]
| Step | Status | Duration |
|---|---|---|
| Pre-flight | ✓ | 5s |
| Backup | ✓ | 2s |
| Deploy | ✓ | 10s |
| Health check | ✓ | 15s |
Post-Deploy Verification
- Service running: ✓
- Health endpoint: 200 OK
- Log errors: 0 in last 60s
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.
- 5d ago First seen · 83 lines · 35 tokens per session scan A 27ec6f552f6a
vibe-safe-deploy is a skill published in the GitHub repository mracal/vibe-engineering (3 stars, last pushed 5d ago), licensed MIT. It adds 35 tokens to every session and 554 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to vibe-safe-deploy, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
agent-workflow-automation
Agent skill for workflow-automation - invoke with $agent-workflow-automation.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
agent-ops-cicd-github
Agent skill for ops-cicd-github - invoke with $agent-ops-cicd-github.
workflow-automation
Workflow creation, execution, and template management. Automates complex multi-step processes with agent coordination. Use when: automating processes, creating reusable workflows, orchestrating multi-step tasks. Skip when: simple single-step tasks, ad-hoc operations.
tutti-app-release
Set up, review, run, or debug external repositories that publish a Tutti workspace app through the reusable Tutti App Release GitHub Actions workflow. Use for caller workflows, tutti.app.json manifests, @tutti-os/app-release-tools, S3/CloudFront release hosting, latest.json, versions.json, catalog.json, catalog-only…