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/bybren-llc/safe-agentic-workflow/release-patternsnpx skills add bybren-llc/safe-agentic-workflow --skill release-patternsgit clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflowWrote 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/safe-agentic-workflow/release-patterns)<a href="https://agentmods.dev/skills/bybren-llc/safe-agentic-workflow/release-patterns"><img src="https://agentmods.dev/badge/skills/bybren-llc/safe-agentic-workflow/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 | $0.00056 | $0.01114 |
| Opus 5 | $0.00028 | $0.00557 |
| Sonnet 5 | $0.00011 | $0.00223 |
| Haiku 4.5 | $0.00006 | $0.00111 |
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 4d 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.
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 [{{TICKET_PREFIX}}-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 {{MAIN_BRANCH}}
CORRECT Patterns
# CORRECT: Ticket reference in title
gh pr create --title "feat(scope): description [{{TICKET_PREFIX}}-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/{{MAIN_BRANCH}}
git push --force-with-lease origin {{TICKET_PREFIX}}-XXX-description
Pre-PR Checklist (MANDATORY)
Before creating any PR:
- Branch name:
{{TICKET_PREFIX}}-{number}-{description} - Commits follow:
type(scope): description [{{TICKET_PREFIX}}-XXX] - Rebased on latest {{MAIN_BRANCH}}:
git fetch origin && git rebase origin/{{MAIN_BRANCH}} - 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 [{{TICKET_PREFIX}}-XXX]" --body "$(cat <<'EOF'
## Summary
Implements [feature/fix] as specified in ticket {{TICKET_PREFIX}}-XXX.
**Ticket**: https://linear.app/{{LINEAR_WORKSPACE}}/issue/{{TICKET_PREFIX}}-XXX
## Changes Made
- Change 1
- Change 2
## Testing
{{CI_VALIDATE_COMMAND}}
# All checks passed
## Pre-merge Checklist
- [x] Rebased on latest {{MAIN_BRANCH}}
- [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.
- 4d ago First seen · 181 lines · 56 tokens per session scan A 99171e2c0ec5
release-patterns is a skill published in the GitHub repository bybren-llc/safe-agentic-workflow (406 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 1,114 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.
bug-report
Creates a structured bug report from a description, or analyzes code to identify potential bugs. Ensures every bug report has full reproduction steps, severity assessment, and context.
security-audit
Java security checklist covering OWASP Top 10, input validation, injection prevention, and secure coding. Works with Spring, Quarkus, Jakarta EE, and plain Java. Use when reviewing code security, before releases, or when user asks about vulnerabilities.
audit-onboarding-proposal
Independently audit a brownfield onboarding transcript, operational map, or exact proposed documentation patch before application. Use when a fresh reviewer must verify an $onboard-repository first pass, distinguish environment-caused Unknowns from reasoning defects, score its safety and evidence gates, or run a…
issue-triage
Triage and categorize GitHub issues with priority labels. Use when user says "triage issues", "check issues", "review open issues", or during regular maintenance of GitHub issue backlog.
engineering-wisdom
Provide an explicitly requested, repository-grounded engineering review using contextual heuristics for code clarity, SOLID and design, testing, refactoring, architecture, and professional practice. Use only when the user invokes $engineering-wisdom or explicitly asks for this installed engineering-wisdom pack; do not…