Borrowing it
Nothing to install: this file belongs to bybren-llc/rendertrust. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bybren-llc/rendertrust/dev/.claude/skills/deployment-sop/SKILL.mdgit clone --depth 1 https://github.com/bybren-llc/rendertrustWrote 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/bybren-llc/rendertrust/deployment-sop)<a href="https://agentmods.dev/skills/bybren-llc/rendertrust/deployment-sop"><img src="https://agentmods.dev/badge/skills/bybren-llc/rendertrust/deployment-sop.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.00033 | $0.00896 |
| Opus 5 | $0.00016 | $0.00448 |
| Sonnet 5 | $0.00007 | $0.00179 |
| Haiku 4.5 | $0.00003 | $0.00090 |
Grade A, and why
deployment-sop 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` How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment SOP Skill
Purpose
Route to existing deployment SOPs and provide checklists for safe, validated deployments. This skill does NOT duplicate SOP content—it links to authoritative sources.
When This Skill Applies
Invoke this skill when:
- Deploying to staging or production
- Running pre-deploy validation
- Executing post-deploy smoke tests
- Accessing Linux dev machine for deployment
- Coordinating release activities
Authoritative References (MUST READ)
| 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 |
Pop OS dev server access |
| Production Server Access | docs/deployment/PRODUCTION-SERVER-ACCESS-SOP.md |
Production deployment |
Pre-Deployment Checklist
Before ANY deployment:
- All CI checks pass (GitHub Actions green)
- PR merged to target branch (
devfor staging,masterfor prod) - No unresolved blockers in Linear
- Database migrations tested locally
- Environment variables verified
# Validate before deploy
yarn ci:validate
yarn 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 (sign-in/sign-up)
- Critical user flows functional
- No new errors in logs (PostHog/Coolify)
# Smoke test commands
curl -s https://{domain}/api/health | jq .
# Expected: {"status":"healthy","timestamp":"..."}
Deployment Evidence Template
For Linear ticket attachment:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 130 lines · 33 tokens per session scan A beb1c7766ff5
deployment-sop is a skill published in the GitHub repository bybren-llc/rendertrust (7 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 896 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-cache
Atmos caching: CI cache configuration and commands, GitHub Actions cache integration, Terraform registry cache mirror/list/prune/stats/trust, and cache modernization guidance.
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.