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 skills add fall-out-bug/sdp --skill verify-workstreamgit 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/skills/fall-out-bug/sdp/verify-workstream)<a href="https://agentmods.dev/skills/fall-out-bug/sdp/verify-workstream"><img src="https://agentmods.dev/badge/skills/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/skills/fall-out-bug/sdp/verify-workstream"><img src="https://agentmods.dev/badge/skills/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.00013 | $0.00180 |
| Opus 5.5 | $0.00005 | $0.00072 |
| Sonnet 5.5 | $0.00003 | $0.00036 |
| Haiku 4.5 | $0.00001 | $0.00018 |
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
Before @build or @oneshot, validate docs match codebase.
Workflow
- Read WS — Parse frontmatter: goal, scope_files, acceptance_criteria
- Find files — Glob to locate scope files. Gate: all must exist
- Read implementation — Parse structure, identify patterns
- Compare — Table: Documentation | Reality | Status
- Recommend — PAUSE (high mismatch) / PROCEED / PROCEED WITH ADAPTATIONS
Output
Verification complete. Severity. Recommendation. Comparison table.
Integration
@build invokes this before execution.
See Also
- @reality-check — Quick single-file check
- @build — Auto-runs verification
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 · 30 lines · 13 tokens per session scan A 061fb5f9623b
verify-workstream is a skill published in the GitHub repository fall-out-bug/sdp (19 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 180 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-09-03.
Other skills, from other repositories
norma-workflow
Run every coding task through Norma's deterministic checks and record the outcome to the audit trail. Use whenever you create or modify code in a workspace connected to the Norma MCP server, when asked to review code against organization standards, or when asked to work through the repository's open issues.
codebase-refactoring
Three-part workflow to improve overall codebase health with jscpd — find and fix duplicated code, find and remove or refactor dead code, then find and simplify the largest/most complex files. Starts from --dashboard/--health to prioritize and ends by re-measuring the score.
prismer-python-debugpy
Debug Python: pdb REPL + debugpy remote (DAP).
debug-live
Guides root-cause investigations with debugging capabilities by setting breakpoints, starting a debug session, stepping through execution, inspecting variables, and tracing symptoms back to their origin. Prefer it for runtime bugs, failing tests, exceptions, crashes, hangs, wrong/null values, and unexpected output…
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits. Triggers: remove dead code, dead code, cleanup, remove unused.
webapp-qa
Perform scoped exploratory QA of a web application, reproduce defects, collect screenshots and console evidence, and deliver a prioritized report.