check-workflow

check-workflow is a command for Claude Code from bybren-llc/safe-agentic-workflow. It costs 7 tokens per session (379 once invoked), scanned A, original, MIT.

A command template for checking the health of a development workflow against project contribution rules.

In plain words
What is it for?
Use it before or during development to inspect Git status, branch naming, Linear ticket connection, commit messages, updates from the dev branch, and related documentation.
Why use it?
It brings branch, ticket, commit, rebase, and documentation checks into one status review so process problems are easier to spot.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/bybren-llc/safe-agentic-workflow/check-workflow
Clone the repo
git clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflow

Made for: Claude Code.

Wrote 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.

agentmods badge for check-workflow

README.md
[![agentmods](https://agentmods.dev/badge/commands/bybren-llc/safe-agentic-workflow/check-workflow.svg)](https://agentmods.dev/commands/bybren-llc/safe-agentic-workflow/check-workflow)
Your own site
<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="Measured on agentmods" height="20"></a>
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 379 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00007 $0.00379
Opus 5 $0.00003 $0.00189
Sonnet 5 $0.00001 $0.00076
Haiku 4.5 $0.00001 $0.00038

Measured 4d ago against content hash 4278e0b63f80, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

.claude/commands/check-workflow.md · 84 lines

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.

Changes

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.

  1. 4d ago First seen · 84 lines · 7 tokens per session scan A 4278e0b63f80

Subscribe to this mod's changes

check-workflow is a command published in the GitHub repository bybren-llc/safe-agentic-workflow (406 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 379 once invoked, about $0.0000 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.