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.
git 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/commands/bybren-llc/safe-agentic-workflow/pre-pr)<a href="https://agentmods.dev/commands/bybren-llc/safe-agentic-workflow/pre-pr"><img src="https://agentmods.dev/badge/commands/bybren-llc/safe-agentic-workflow/pre-pr/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/commands/bybren-llc/safe-agentic-workflow/pre-pr"><img src="https://agentmods.dev/badge/commands/bybren-llc/safe-agentic-workflow/pre-pr.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.00007 | $0.00593 |
| Opus 5.5 | $0.00003 | $0.00237 |
| Sonnet 5.5 | $0.00001 | $0.00119 |
| Haiku 4.5 | $0.00001 | $0.00059 |
Grade A, and why
pre-pr 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.
How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
📋 TEMPLATE: This command is a template. See "Customization Guide" below to adapt for your infrastructure.
You are preparing to create a Pull Request. Execute the MANDATORY @CONTRIBUTING.md validation workflow:
Validation Checklist
1. Code Quality Validation
Run CI validation suite:
yarn ci:validate
This runs:
- TypeScript type checking
- ESLint validation
- Unit tests
- Format checking
BLOCKER: Must pass before proceeding. Fix any failures.
2. Documentation Linting
Auto-fix markdown formatting:
yarn lint:md:fix
Verify no errors remain:
yarn lint:md
3. Git Status Check
Verify all changes committed:
git status
BLOCKER: No uncommitted changes allowed in PR.
4. Rebase onto Latest Dev
Fetch and rebase:
git fetch origin
git rebase origin/dev
BLOCKER: Must be up-to-date with dev branch.
5. Commit Message Validation
Check all commits follow SAFe format:
git log origin/dev..HEAD --oneline
Required format: type(scope): description [{{TICKET_PREFIX}}-XXX]
BLOCKER: All commits must reference Linear ticket.
6. Documentation Updates
Verify related docs updated:
- CLAUDE.md (if architecture/workflow changed)
- CONTRIBUTING.md (if process changed)
- Specialized docs (feature-specific)
7. PR Template Ready
Confirm you can fill out ALL sections:
- 📋 Summary with Linear ticket link
- 🎯 Changes Made
- 🧪 Testing
- 📊 Impact Analysis
- 🔄 Multi-Team Coordination
- ✅ Pre-merge Checklist
Workflow
Execute steps 1-6 in order.
Report results for each step:
- ✅ PASS: Step completed successfully
- ⚠️ WARNING: Non-blocking issue found
- ❌ BLOCKER: Must fix before PR
Success Criteria
All validation steps pass. Ready to create PR with:
git push --force-with-lease origin {branch-name}
gh pr create --title "..." --body "..."
Report final status and any remaining blockers.
Customization Guide
To adapt this command for your infrastructure, replace these placeholders:
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 · 123 lines · 7 tokens per session scan A b6509f83e13a
pre-pr is a command published in the GitHub repository bybren-llc/safe-agentic-workflow (424 stars, last pushed 3mo ago), licensed MIT. It adds 7 tokens to every session and 593 once invoked, about $0.0000 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 commands, from other repositories
check
Run project checks and fix any errors without committing.
act
Follow RED-GREEN-REFACTOR cycle approach for test-driven development.
implement
Execute all implementation tasks from tasks.md with test-driven development, parallel batching, and atomic commits.
validate
Command "validate" from Vimalk0703/shipworthy, covering /validate — pre-push validation gate, what this does, steps, when to run and output format.
gather
Phase 40 — merge completed SPs in wave order, run per-SP regression, update wave-status.
implement-feature
Implement an approved feature plan with fresh-context slices, TDD, revision-bound evidence, and PR-ready output.