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 safe-workflowgit 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/safe-workflow)<a href="https://agentmods.dev/skills/bybren-llc/a-safe-pulse/safe-workflow"><img src="https://agentmods.dev/badge/skills/bybren-llc/a-safe-pulse/safe-workflow/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/a-safe-pulse/safe-workflow"><img src="https://agentmods.dev/badge/skills/bybren-llc/a-safe-pulse/safe-workflow.svg" alt="Reviewed on agentmods" width="80" 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.00052 | $0.00626 |
| Opus 5 | $0.00026 | $0.00313 |
| Sonnet 5 | $0.00010 | $0.00125 |
| Haiku 4.5 | $0.00005 | $0.00063 |
Grade A, and why
safe-workflow 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.
This is a copy
88% identical to safe-workflow — 26 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAFe Workflow Skill
TEMPLATE: This skill uses
ASPas a placeholder. Replace with your project's ticket prefix (e.g.,WOR,PROJ,FEAT).
Purpose
Enforce SAFe-compliant git workflow with standardized branch naming, commit message format, and rebase-first merge strategy.
When This Skill Applies
- Starting work on a ticket
- Creating commits or branches
- Asking about PR workflow or contribution guidelines
- Asking "how should I commit this?"
Branch Naming Convention
Format: ASP-{number}-{short-description}
# Good
ASP-447-create-safe-workflow-skill
ASP-123-fix-login-redirect
# Bad
feature/add-dark-mode (missing ticket number)
john-new-feature (personal naming)
Commit Message Format
Format: type(scope): description [ASP-XXX]
| Type | When to Use |
|---|---|
feat |
New feature |
fix |
Bug fix |
docs |
Documentation only |
refactor |
Code restructuring |
test |
Adding or updating tests |
chore |
Maintenance, dependencies |
feat(harness): create safe-workflow skill [ASP-447]
fix(auth): resolve login redirect [ASP-57]
Rebase-First Workflow
# 1. Start from latest main
git checkout dev && git pull origin dev
# 2. Create feature branch
git checkout -b ASP-{number}-{description}
# 3. Make commits
git commit -m "type(scope): description [ASP-XXX]"
# 4. Before pushing - rebase
git fetch origin && git rebase origin/dev
# 5. Push with force-with-lease
git push --force-with-lease
Pre-PR Checklist
- Branch name follows convention
- All commits have ticket reference
- Rebased on latest main
- CI passes:
{{CI_VALIDATE_COMMAND}}
Evidence Template
When closing a ticket, attach evidence:
**Work Evidence**
**Ticket**: ASP-XXX
**Branch**: ASP-XXX-description
**PR**: #NNN
**Commits:**
- type(scope): description
**Validation:**
- CI: PASS
- Tests: X/X passing
- Lint: Clean
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 · 107 lines · 52 tokens per session scan A 9d03cf1aa2a0
safe-workflow is a skill published in the GitHub repository bybren-llc/a-safe-pulse (9 stars, last pushed 5mo ago), licensed MIT. It adds 52 tokens to every session and 626 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 safe-workflow, differing in 26 lines, and is treated as a copy.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…