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 bybren-llc/a-safe-pulse --skill release-patternsgit 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/skills/bybren-llc/a-safe-pulse/release-patterns)<a href="https://agentmods.dev/skills/bybren-llc/a-safe-pulse/release-patterns"><img src="https://agentmods.dev/badge/skills/bybren-llc/a-safe-pulse/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.00056 | $0.01049 |
| Opus 5 | $0.00028 | $0.00524 |
| Sonnet 5 | $0.00011 | $0.00210 |
| Haiku 4.5 | $0.00006 | $0.00105 |
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 3d 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
88% identical to release-patterns — 34 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Patterns Skill
TEMPLATE: This skill uses
{{PLACEHOLDER}}tokens. Replace with your project values before use.
Purpose
Ensure consistent PR creation, CI/CD validation, and release coordination following rebase-first workflow.
When This Skill Applies
- Creating pull requests
- Running pre-PR validation
- 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 [ASP-XXX]
# FORBIDDEN: Using squash/merge commits (breaks linear history)
gh pr merge --squash
gh pr merge --merge
# FORBIDDEN: Skipping CI validation
git push origin feature # Without {{CI_VALIDATE_COMMAND}} 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 [ASP-XXX]"
# CORRECT: Rebase merge only
gh pr merge --rebase --delete-branch
# CORRECT: CI validation before push
{{CI_VALIDATE_COMMAND}} && git push --force-with-lease
# CORRECT: Always rebase first
git fetch origin && git rebase origin/dev
git push --force-with-lease origin ASP-XXX-description
Pre-PR Checklist (MANDATORY)
Before creating any PR:
- Branch name:
ASP-{number}-{description} - Commits follow:
type(scope): description [ASP-XXX] - Rebased on latest dev:
git fetch origin && git rebase origin/dev - CI passes locally:
{{CI_VALIDATE_COMMAND}} - Linear history: No merge commits (
git log --oneline --graph -10)
CI/CD Validation Command
# MANDATORY before any PR
{{CI_VALIDATE_COMMAND}} && echo "READY FOR PR" || echo "FIX ISSUES FIRST"
PR Creation Template
gh pr create --title "feat(scope): description [ASP-XXX]" --body "$(cat <<'EOF'
## Summary
Implements [feature/fix] as specified in ticket ASP-XXX.
**Ticket**: https://linear.app/cheddarfox/issue/ASP-XXX
## Changes Made
- Change 1
- Change 2
## Testing
{{CI_VALIDATE_COMMAND}}
# All checks passed
## Pre-merge Checklist
- [x] Rebased on latest dev
- [x] CI passes
- [x] Ticket referenced
EOF
)"
What ships with it
3 files 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.
- 3d ago First seen · 181 lines · 56 tokens per session scan A e7127c1557c1
release-patterns is a skill published in the GitHub repository bybren-llc/a-safe-pulse (9 stars, last pushed 5mo ago), licensed MIT. It adds 56 tokens to every session and 1,049 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to release-patterns, differing in 34 lines, and is treated as a copy.
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).
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…
seed-snapshot-release
An automated workflow for creating and tracking a snapshot release of the pull request on the current branch. A snapshot release is a temporary package build used for testing a branch before a normal release.
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
release-engineering
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness. Use when preparing a release, shipping a risky PR, coordinating app/backend/database rollout, recovering from a bad deploy, or defining release…
cmux-release
Prefer the /release command. It determines the new version (minor by default), gathers commits since the last tag, updates CHANGELOG.md, runs ./scripts/bump-version.sh, commits, runs ./scripts/release-pretag-guard.sh, then tags and pushes.