Borrowing it
Nothing to install: this file belongs to phuoctrung-ppt/ai-sdlc-workflow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/phuoctrung-ppt/ai-sdlc-workflow/master/.cursor/commands/workflow-eval.mdgit clone --depth 1 https://github.com/phuoctrung-ppt/ai-sdlc-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/phuoctrung-ppt/ai-sdlc-workflow/workflow-eval)<a href="https://agentmods.dev/commands/phuoctrung-ppt/ai-sdlc-workflow/workflow-eval"><img src="https://agentmods.dev/badge/commands/phuoctrung-ppt/ai-sdlc-workflow/workflow-eval/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/phuoctrung-ppt/ai-sdlc-workflow/workflow-eval"><img src="https://agentmods.dev/badge/commands/phuoctrung-ppt/ai-sdlc-workflow/workflow-eval.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.00018 | $0.00351 |
| Opus 5.5 | $0.00007 | $0.00140 |
| Sonnet 5.5 | $0.00004 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
workflow-eval 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.
What it actually says
Act as Judge Agent with the workflow integrity checklist. Always write a durable artifact under docs/reviews/, whether this command was invoked manually or by a protected-change hook.
Evaluate: {plan_or_diff_or_feature}
Inputs to inspect:
AGENTS.md- Standards docs from
.cursor/config/workflow-policy.json, usuallyAGENTS.md - Relevant
docs/plans/*ordocs/adr/* - Relevant
.cursor/agents/*,.cursor/rules/*,.cursor/commands/* - Git diff or specified implementation files
Process:
- Run context-builder for review:
python3 .cursor/context/context-builder.py --phase review --task "{plan_or_diff_or_feature}" --agent judge-agent --keywords "workflow,judge,security,tenant,test" --budget 5000 - Verify the result against acceptance criteria and the handoff packet.
- Check the shared protected classifier in
.cursor/config/protected-paths.json; do not accept agent self-classification. - Check role boundaries: planner planned, workers implemented, judge stayed read-only.
- Check evidence quality: commands, tests, docs, ADRs, security/privacy/data/AI/infrastructure/domain gates.
- Write findings to
docs/reviews/YYYY-MM-DD-workflow-eval-{slug}.md.
Output:
Status: GOOD | NEEDS_OPTIMIZATION | BLOCKED
## What Works
## Gaps
- [severity] file:line — issue
## Required Optimizations
## Evidence Reviewed
## Recommended Cursor Config 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.
- 1mo ago First seen · 42 lines · 18 tokens per session scan A 44acf2e9e794
workflow-eval is a command published in the GitHub repository phuoctrung-ppt/ai-sdlc-workflow (2 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 351 once invoked, about $0.0001 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-31.
Other commands, from other repositories
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
refactor
Systematic code refactoring with smart scope detection.
init
Install the formatters this repository needs, with every command visible before it runs.
spec-trace-requirements
You are verifying that implementation changes trace back to specification requirements.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
boot
Start a new PromptKit prompt assembly session (alias for /bootstrap).