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/fall-out-bug/sdpWrote 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/fall-out-bug/sdp/verify-workstream)<a href="https://agentmods.dev/commands/fall-out-bug/sdp/verify-workstream"><img src="https://agentmods.dev/badge/commands/fall-out-bug/sdp/verify-workstream/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/fall-out-bug/sdp/verify-workstream"><img src="https://agentmods.dev/badge/commands/fall-out-bug/sdp/verify-workstream.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.00009 | $0.00144 |
| Opus 5.5 | $0.00004 | $0.00058 |
| Sonnet 5.5 | $0.00002 | $0.00029 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
verify-workstream 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
/verify-workstream — Verify-workstream
Overview
This command implements the verify-workstream skill from the SDP workflow.
See /prompts/skills/verify-workstream/SKILL.md for complete documentation.
Usage
/verify-workstream [arguments]
Implementation
The command delegates to the verify-workstream skill, which provides:
- Systematic workflow
- Quality gates
- Proper error handling
- Documentation
Related
- Skills:
prompts/skills/verify-workstream/SKILL.md - Agents:
prompts/agents/builder.md
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 · 33 lines · 9 tokens per session scan A bd9f73fc7c14
verify-workstream is a command published in the GitHub repository fall-out-bug/sdp (19 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 144 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
refactor-clean
Refactor provided code for cleanliness, maintainability, and alignment with SOLID principles and modern best practices — no over-engineering.
parallel-analyze
Multi-perspective analysis using parallel subagents. Analyzes code from architecture, security, performance, and testing viewpoints simultaneously.
parallel-review
Run parallel code review across multiple directories or files. Uses N subagents simultaneously for faster analysis.
init
Install the formatters this repository needs, with every command visible before it runs.
simplify
The over-engineering review: five tags (delete, stdlib, native, yagni, shrink), a mandatory replacement per finding, and a real null result when there is nothing to cut.
review-code
Read ALL memory bank code rules + best practices, check the files that changed, and APPLY fixes so they adhere. The active counterpart to /scan (which is read-only). Use after an AI session, before commit, to make changed files compliant.