Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add MostAshraf/ai-sdlc-harness/plugin install ai-sdlc-harnessWrote 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/mostashraf/ai-sdlc-harness/story-workflow)<a href="https://agentmods.dev/skills/mostashraf/ai-sdlc-harness/story-workflow"><img src="https://agentmods.dev/badge/skills/mostashraf/ai-sdlc-harness/story-workflow/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/mostashraf/ai-sdlc-harness/story-workflow"><img src="https://agentmods.dev/badge/skills/mostashraf/ai-sdlc-harness/story-workflow.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.00099 | $0.00930 |
| Opus 5 | $0.00049 | $0.00465 |
| Sonnet 5 | $0.00020 | $0.00186 |
| Haiku 4.5 | $0.00010 | $0.00093 |
Grade A, and why
story-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 10d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
story-workflow — story-quality refinement (PO-facing)
Improves work-item quality through four commands. Read-mostly: it fetches a
work item, helps shape it, and — only with the user's consent — posts the
result back as a comment. It never starts a dev run and never touches
ai/<run>/ run state.
Every harness call is ${CLAUDE_PLUGIN_ROOT}/bin/harness <verb> … — the full
path, run by you via Bash (a bare harness is not on PATH, and shell variables
set in one Bash call do not persist to the next). Non-zero exit = refused; read
the JSON error and act on it.
Usage
/story-workflow <command> <work-item-id> [session-notes…]
<command> is one of analyze, refine, improve, groom. <work-item-id>
is whatever the configured provider uses — a number (ADO / GitHub / GitLab), a
key (PROJ-123, Jira), or, for local-markdown, the story's id (the file
stem inside provider.stories_dir, e.g. WORK-7 for WORK-7.md — not a
path). Any trailing tokens are session notes, passed through to improve and
refine.
Routing
| command | file | one-line |
|---|---|---|
improve |
commands/improve.md |
adaptive single-pass: assess → gap-fill → draft (the recommended default) |
analyze |
commands/analyze.md |
standalone readiness report with flags |
refine |
commands/refine.md |
slow, section-by-section interactive restructure |
groom |
commands/groom.md |
codebase-aware per-repo technical notes |
Parse $ARGUMENTS: the first token is the command, the second is the work-item
id, the rest are notes. If the command is missing or unknown, print the usage
line plus the table above and stop — do not guess. If the id is missing, ask
for it — never proceed without one. Then read the one matching command file and
follow it (context economy: load a single command file, not all four).
Before routing
- Confirm the workspace is bootstrapped:
.claude/context/provider.yamlmust exist. If it doesn't,/init-workspacenever ran — send the user there and stop. The active provider is resolved from config by the harness; you never hand-pick it. - The recipe for fetching a work item and posting a result back — for every
provider and both transports — lives once in
shared/provider-io.md. Read it; the commands cite it instead of repeating it. - Domain and convention context (for
improveandgroom) lives once inshared/context.md.
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 77 lines · 99 tokens per session scan A c645fdc9cb2d
story-workflow is a skill published in the GitHub repository MostAshraf/ai-sdlc-harness (19 stars, last pushed 14d ago), licensed MIT. It adds 99 tokens to every session and 930 once invoked, about $0.0005 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.
Other skills, from other repositories
autonomous
Run multiple phases hands-free. Chains discuss, plan, build, and verify automatically.
quick
Execute an ad-hoc task with atomic commits. Skips full plan/review.
audit
Review past Claude Code sessions for PBR workflow compliance and UX quality.
resume
Pick up where you left off. Restores context and suggests next action.
status
Show current project status and suggest what to do next.
config
Configure settings: depth, model profiles, features, git, and gates.