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 rules/bybren-llc/a-safe-pulse/15-deploymentgit clone --depth 1 https://github.com/bybren-llc/a-safe-pulseWrote 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/rules/bybren-llc/a-safe-pulse/15-deployment)<a href="https://agentmods.dev/rules/bybren-llc/a-safe-pulse/15-deployment"><img src="https://agentmods.dev/badge/rules/bybren-llc/a-safe-pulse/15-deployment.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.1 | $0.00000 | $0.00867 |
| Opus 5 | $0.00000 | $0.00434 |
| Sonnet 5 | $0.00000 | $0.00173 |
| Haiku 4.5 | $0.00000 | $0.00087 |
Grade A, and why
15-deployment 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- [ ] Health endpoint responds: `curl https://{domain}/api/health` This is a copy
89% identical to 15-deployment — 6 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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment Rules
These rules apply when working on deployment configurations, Docker files, or executing deployments.
Authoritative SOPs (MUST READ before deploying)
| Document | Location | Purpose |
|---|---|---|
| Semantic Release SOP | docs/ci-cd/Semantic-Release-Deployment-SOP.md |
Release automation workflow |
| Staging/UAT Release SOP | docs/sop/STAGING-UAT-RELEASE-SOP.md |
UAT validation process |
| Linux Dev Machine Access | docs/deployment/LINUX-DEV-MACHINE-ACCESS-SOP.md |
Dev server access |
| Production Server Access | docs/deployment/PRODUCTION-SERVER-ACCESS-SOP.md |
Production deployment |
Always read the relevant SOP before proceeding. This rule provides checklists, not full procedures.
Pre-Deployment Checklist
Before ANY deployment:
- All CI checks pass (GitHub Actions green)
- PR merged to target branch (
{{DEV_BRANCH}}for staging,devfor prod) - No unresolved blockers in Linear
- Database migrations tested locally
- Environment variables verified
# Validate before deploy
{{CI_VALIDATE_COMMAND}}
docker compose build
Post-Deployment Smoke Test
After deployment completes:
- Health endpoint responds:
curl https://{domain}/api/health - Database connection verified (check health response)
- Authentication flow works
- Critical user flows functional
- No new errors in logs
# Smoke test
curl -s https://{domain}/api/health | jq .
# Expected: {"status":"healthy","timestamp":"..."}
Branch to Environment Mapping
| Branch | Environment | Auto-Deploy |
|---|---|---|
{{DEV_BRANCH}} |
Staging | Manual pull |
dev |
Production (Coolify) | Automatic |
Rollback Procedure
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 · 118 lines · 0 tokens per session scan A f8f9a2ebf93f
15-deployment is a cursor rule published in the GitHub repository bybren-llc/a-safe-pulse (9 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 867 tokens. A static security scan graded it A with 1 finding (makes network calls). It is 89% identical to 15-deployment, differing in 6 lines, and is treated as a copy.
Other cursor rules, from other repositories
infra-deploy
ZizkaDB infrastructure, Docker Compose, deployment, CI/CD, and scripts.
90-devops-deployment
Docker, CI/CD, AWS, Vercel, and VPS deployment rules.
deploy-arch-maintenance
部署架构文档维护规则（RULE-21/22/23/24/25）。当任务涉及部署、服务器、容器、端口、域名、CI/CD、新项目上线、技术架构设计、数据库操作时自动激活。.
infra-devops
Infrastructure, Cloud, Terraform, Docker & CI/CD Agent.
devops
DevOps Engineer - Docker, CI/CD, Cloud Deployment.
deployment-engineer-intelligent
CI/CD and deployment automation specialist for containerized applications. Apply this rule when configuring CI/CD pipelines (GitHub Actions, GitLab CI, Jenkins), creating Docker containers with multi-stage builds, setting up Kubernetes deployments and services, implementing Infrastructure as Code, configuring…