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/check-workflow)<a href="https://agentmods.dev/commands/bybren-llc/safe-agentic-workflow/check-workflow"><img src="https://agentmods.dev/badge/commands/bybren-llc/safe-agentic-workflow/check-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/commands/bybren-llc/safe-agentic-workflow/check-workflow"><img src="https://agentmods.dev/badge/commands/bybren-llc/safe-agentic-workflow/check-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.00007 | $0.00379 |
| Opus 5.5 | $0.00003 | $0.00152 |
| Sonnet 5.5 | $0.00001 | $0.00076 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
check-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 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
2 near-identical copies found in the catalogue:
- check-workflow — 92% identical, 6 lines differ
- check-workflow — 91% identical, 6 lines differ
What it actually says
Perform a quick workflow health check against @CONTRIBUTING.md requirements.
Status Checks
1. Git Status
git status
git branch --show-current
Verify:
- Current branch follows
{{TICKET_PREFIX}}-{number}-{description}format - No uncommitted changes (or document what's uncommitted)
- Branch relationship to origin/dev
2. Linear Ticket Connection
Extract WOR number from branch name.
Check ticket status using Linear MCP:
mcp__{{MCP_LINEAR_SERVER}}__get_issue
Verify:
- Ticket exists
- Ticket is in appropriate status
- Work aligns with ticket description
3. Commit History
Review commits since dev:
git log origin/dev..HEAD --oneline
Verify:
- All commits follow SAFe format:
type(scope): description [{{TICKET_PREFIX}}-XXX] - All commits reference correct Linear ticket
- Commit messages are descriptive
4. Rebase Status
Check if branch needs rebasing:
git fetch origin
git log HEAD..origin/dev --oneline
Report:
- How many commits behind dev
- Whether rebase is needed
5. Documentation Status
Check if docs need updating:
- CLAUDE.md (architecture/commands changed?)
- CONTRIBUTING.md (process changed?)
- Feature-specific docs created?
Output Format
Provide traffic-light status:
- ✅ GREEN: All checks pass, workflow healthy
- ⚠️ YELLOW: Minor issues, can proceed with caution
- ❌ RED: Blockers present, must fix before PR
List specific issues found and recommendations.
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 · 84 lines · 7 tokens per session scan A 4278e0b63f80
check-workflow is a command published in the GitHub repository bybren-llc/safe-agentic-workflow (425 stars, last pushed 3mo ago), licensed MIT. It adds 7 tokens to every session and 379 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
ship
Deploy feature through automated staging validation to production with rollback testing.
clarify
Reduce spec ambiguity via targeted questions with adaptive auto-invocation (planning is 80% of success).
help
Analyze workflow state and provide context-aware guidance with visual progress indicators and recommended next steps.
init
Initialize project documentation, preferences, or design tokens.
help
Category: System Syntax: /help [command|topic].
review-tasks
A command that reviews a task list for fidelity to its source plans, practical executability, dependencies, and ways to verify completion. It can use project requirements, specifications, designs, plans, and repository files.