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 MageByte-Zero/spec-superflow --skill workflow-startgit clone --depth 1 https://github.com/MageByte-Zero/spec-superflowWrote 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/magebyte-zero/spec-superflow/workflow-start)<a href="https://agentmods.dev/skills/magebyte-zero/spec-superflow/workflow-start"><img src="https://agentmods.dev/badge/skills/magebyte-zero/spec-superflow/workflow-start/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/magebyte-zero/spec-superflow/workflow-start"><img src="https://agentmods.dev/badge/skills/magebyte-zero/spec-superflow/workflow-start.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00061 | $0.01036 |
| Opus 5.5 | $0.00024 | $0.00414 |
| Sonnet 5.5 | $0.00012 | $0.00207 |
| Haiku 4.5 | $0.00006 | $0.00104 |
Grade A, and why
workflow-start 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.
How it starts
The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Start
Bundled runtime
Before executing a CLI line below, replace its leading SSF with node "<plugin-root>/scripts/spec-superflow.mjs"; <plugin-root> is the absolute directory two levels above this file. Never run SSF literally or call an ssf from PATH.
Use only for an explicit spec-superflow request or an existing change. Ordinary coding does not require a spec workflow.
Resume
Run SSF resume <change-dir> --json once. It combines state, handoffs, checkpoints and current-plan inspection. Use the returned absolute change.path for all subsequent operations: recovery may redirect a stale source copy into its recorded worktree. Follow next_action; do not repeat all component commands unless diagnosing that result. A blocked continuation is not a retry instruction; resolve its named cause before running it again. Read only the artifacts relevant to the next action.
debugging: diagnose first, even if a plan is stale. Never dispatch an eligible wave during diagnosis.closing: logical completion. If a recorded isolation still has physical finish pending, route to release-archivist for that remaining action, subject to existing merge authorization. Otherwise stop.abandoned: stop.- A ready handoff needs review through
SSF handoff resolve; an active handoff is non-blocking. Stale checkpoints are history, not current evidence. - Missing/stale Full plans block implementation, not investigation. Valid short paths and Tweak do not require plans.
Update checks are optional (SSF runtime check-update), cached and non-blocking. Never make network access a recovery prerequisite.
New request
Infer scope and risks from the request and repository; do not turn CLI fields into a questionnaire. Validate the change name as a single safe relative path segment under changes/ and create only that directory. Reuse authorization already given. Never infer approval from artifact existence.
Offer only two paths, without a mode-selection interview:
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 Changed · +4 lines c9a55cd09dcd
- 1mo ago Changed · -223 lines · -64 tokens per session 6094331dda52
- 1mo ago Changed e000ec45f6af
- 1mo ago First seen · 263 lines · 125 tokens per session scan A 029137c0b76b
workflow-start is a skill published in the GitHub repository MageByte-Zero/spec-superflow (873 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 1,036 once invoked, about $0.0002 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 skills, from other repositories
chinese-documentation
A Chinese technical-documentation style guide covering spacing, punctuation, numbers, terminology, and links when Chinese and English appear together.
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
acceptance-test-authoring
Use when creating or modifying acceptance tests, configuring cucumber-js or behave runners, writing or refactoring step definitions, linting executable Gherkin specs, choosing an acceptance stack, or implementing OpenSpec tasks that involve acceptance tests.
openspec-bulk-apply-change
Use when multiple active OpenSpec changes should be applied concurrently in isolated worktrees with delegated verification and no merge.
task-to-pr
Delivers specs or decided tasks as tested, independently reviewed pull requests. Runs the CI and review repair loop, then leaves passing pull requests open unless merging was explicitly authorized.
factory
Delivers a spec or decided task through the task-to-pr workflow and merges after all quality and approval gates pass. Explicit invocation grants merge authority for the supplied work.