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 agentmods add commands/c0ntr0lledcha0s/claude-code-plugin-automations/workflow-statusgit clone --depth 1 https://github.com/C0ntr0lledCha0s/claude-code-plugin-automationsWrote 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/c0ntr0lledcha0s/claude-code-plugin-automations/workflow-status)<a href="https://agentmods.dev/commands/c0ntr0lledcha0s/claude-code-plugin-automations/workflow-status"><img src="https://agentmods.dev/badge/commands/c0ntr0lledcha0s/claude-code-plugin-automations/workflow-status.svg" alt="Measured on agentmods" 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 | $0.00019 | $0.00972 |
| Opus 5 | $0.00010 | $0.00486 |
| Sonnet 5 | $0.00004 | $0.00194 |
| Haiku 4.5 | $0.00002 | $0.00097 |
Grade A, and why
workflow-status 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 5d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Status
Display current GitHub workflow state and suggest next actions.
Usage
/workflow-status
What This Shows
- Current Branch: Name, ahead/behind main, related issues, detected scope
- Tracked Issues: Issues from local cache, grouped by context:
- Branch Issues: Issues selected for current branch (from
relatedIssues) - Scope-Relevant: Issues matching branch's detected scope label
- Project Issues: Other issues in default project board
- All Other: Remaining cached issues
- Branch Issues: Issues selected for current branch (from
- Recent Commits: Last 5 commits on branch with issue references
- Open PRs: From this branch or assigned to you
- Project Boards: Issues in boards
- Pending Reviews: PRs awaiting your review
- Next Actions: Suggested next steps based on issues and commits
Example Output
Current Branch: feature/auth
5 commits ahead of main
Last commit: feat(auth): add JWT validation
Detected scope: auth (scope:auth)
Selected issues: #42, #43
📋 BRANCH ISSUES (selected for this branch):
#42: Implement JWT authentication [In Progress]
Labels: feature, priority:high, scope:auth
#43: Add JWT validation [Open]
Labels: feature, scope:auth
📋 SCOPE-RELEVANT (matching scope:auth):
#56: Fix login validation error [Open]
Labels: bug, priority:high, scope:auth
📋 PROJECT ISSUES (in Agent Plugin Development):
#78: Add password reset feature [Open]
Labels: feature, scope:api
📋 OTHER CACHED ISSUES:
#89: Update documentation [Open]
Labels: docs
Recent Commits on Branch:
abc1234 feat(auth): add JWT validation (Refs #42)
def5678 feat(auth): add token service (Refs #42)
ghi9012 test(auth): add JWT tests
Open PRs:
#123: feat(auth): add JWT authentication (ready to merge)
Closes #42, Closes #43
Project Boards:
Sprint 5: 3 issues assigned to you
- #42: In Progress
- #43: Todo
- #45: Todo
Pending Reviews:
#124: fix(api): resolve validation (awaiting your review)
Next Actions:
1. Merge PR #123 (all checks passed) - will close #42, #43
2. Review PR #124
3. Start work on issue #56 (scope-relevant, high priority)
4. Sync issues: /issue-track sync (cache is 10 min old)
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.
- 5d ago First seen · 114 lines · 19 tokens per session scan A 2f326466c39a
workflow-status is a command published in the GitHub repository C0ntr0lledCha0s/claude-code-plugin-automations (3 stars, last pushed 6mo ago), licensed MIT. It adds 19 tokens to every session and 972 once invoked, about $0.0001 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.