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/release-patterns/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/release-patterns)<a href="https://agentmods.dev/skills/bybren-llc/rendertrust/release-patterns"><img src="https://agentmods.dev/badge/skills/bybren-llc/rendertrust/release-patterns.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.00036 | $0.00876 |
| Opus 5 | $0.00018 | $0.00438 |
| Sonnet 5 | $0.00007 | $0.00175 |
| Haiku 4.5 | $0.00004 | $0.00088 |
Grade A, and why
release-patterns 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 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.
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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Patterns Skill
Purpose
Ensure consistent PR creation, CI/CD validation, and release coordination following rebase-first workflow.
When This Skill Applies
Invoke this skill when:
- Creating pull requests
- Running pre-PR validation (
yarn ci:validate) - Checking CI/CD status
- Coordinating merge timing
- Verifying rebase status
Stop-the-Line Conditions
FORBIDDEN Patterns
# FORBIDDEN: Missing ticket reference
gh pr create --title "feat: add feature" # Missing [REN-XXX]
# FORBIDDEN: Using squash/merge commits
gh pr merge --squash # Breaks linear history
gh pr merge --merge # Creates merge commit
# FORBIDDEN: Skipping CI validation
git push origin feature # Without yarn ci:validate first
# FORBIDDEN: Pushing without rebase
git push origin feature # When branch is behind dev
CORRECT Patterns
# CORRECT: Ticket reference in title
gh pr create --title "feat(scope): description [REN-XXX]"
# CORRECT: Rebase merge only
gh pr merge --rebase --delete-branch
# CORRECT: CI validation before push
yarn ci:validate && git push --force-with-lease
# CORRECT: Always rebase first
git fetch origin && git rebase origin/dev
git push --force-with-lease origin REN-XXX-description
Pre-PR Checklist (MANDATORY)
Before creating any PR:
- Branch name:
REN-{number}-{description} - Commits follow:
type(scope): description [REN-XXX] - Rebased on latest dev:
git fetch origin && git rebase origin/dev - CI passes locally:
yarn ci:validate - Linear history: No merge commits (
git log --oneline --graph -10)
CI/CD Validation Command
# MANDATORY before any PR
yarn ci:validate && echo "READY FOR PR" || echo "FIX ISSUES FIRST"
PR Creation Template
gh pr create --title "feat(scope): description [REN-XXX]" --body "$(cat <<'EOF'
## Summary
Implements [feature/fix] as specified in Linear ticket REN-XXX.
**Linear Ticket**: https://linear.app/bybren/issue/REN-XXX
## Changes Made
- Change 1
- Change 2
## Testing
```bash
yarn ci:validate
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 · 140 lines · 36 tokens per session scan A c6ca900ac887
release-patterns is a skill published in the GitHub repository bybren-llc/rendertrust (7 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 876 once invoked, about $0.0002 per session on Opus 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-04.
Other skills, from other repositories
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. (gstack).
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
seed-snapshot-release
Drives the snapshot-release flow for the current branch's PR. Posts a /snapshot comment on the PR if one isn't already there (with confirmation), waits for the Continuous Releases workflow to finish, and reports the tarball URLs from the resulting 📦 Snapshot Release comment. Use for both triggering and waiting …
releasepr
Adopt, configure, run, or troubleshoot compozy/releasepr in a consuming repository, including Actions, beta/stable/legacy plans, notes, dry-runs, and publication. Excludes pr-release internals and general versioning advice.
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…