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/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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<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="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 39 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.01114 |
| Opus 5.5 | $0.00022 | $0.00446 |
| Sonnet 5.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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- release-patterns — 88% identical, 34 lines differ
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.
- 1mo 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 (425 stars, last pushed 3mo ago), licensed MIT. It adds 56 tokens to every session and 1,114 once invoked, about $0.0002 per session on Opus 5.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
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.
changelog
Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.
team-release
Orchestrate the release team — release-manager, qa-lead, devops-engineer, producer — to execute a release from candidate to deployment.
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…