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 medalsoftchina/workcopilot --skill spec-flow-maingit clone --depth 1 https://github.com/medalsoftchina/workcopilotWrote 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/medalsoftchina/workcopilot/spec-flow-main)<a href="https://agentmods.dev/skills/medalsoftchina/workcopilot/spec-flow-main"><img src="https://agentmods.dev/badge/skills/medalsoftchina/workcopilot/spec-flow-main.svg" alt="Measured on agentmods" 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.00061 | $0.03120 |
| Opus 5 | $0.00030 | $0.01560 |
| Sonnet 5 | $0.00012 | $0.00624 |
| Haiku 4.5 | $0.00006 | $0.00312 |
Grade A, and why
spec-flow 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 7d 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 — 394 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-Flow - Structured Development Workflow
Structured workflow for complex feature development. Creates living documentation that guides implementation and serves as team reference.
⚠️ Interaction Rules (MUST Follow)
This skill uses a phase-by-phase confirmation workflow, ensuring users can review and adjust at each stage.
Language Rule
All generated documents (.md files) MUST be written in Chinese (中文), including:
- proposal.md, requirements.md, design.md, tasks.md
- Section headings, descriptions, requirements text, task descriptions
- Comments and notes within documents
Core Principles
- One phase at a time: Only work on the current phase. NEVER generate documents for subsequent phases in advance.
- Mandatory confirmation: After completing each phase, you MUST stop and wait for user confirmation.
- User-driven progression: Only proceed to the next phase when user explicitly says "continue", "ok", "next", "looks good", "继续", "好", "下一步", etc.
Confirmation Template
After completing each phase, you MUST use this format to request confirmation:
📋 **[Phase Name] Complete**
Created `.spec-flow/active/<feature>/<file>.md` containing:
- [Key content summary]
**Please review**:
1. [Review question]?
2. [Review question]?
✅ Say "continue" to proceed to next phase
✏️ Tell me what to modify if needed
❌ Prohibited Behaviors
- Generating multiple phase documents after user describes a feature
- Automatically proceeding to next phase without user confirmation
- Creating both proposal.md and requirements.md in one response
- Assuming user wants to skip confirmation for speed
✅ Correct Flow Example
User: I want to implement user authentication
AI: [Creates only proposal.md] + confirmation prompt
User: continue
AI: [Creates only requirements.md] + confirmation prompt
User: looks good, next
AI: [Creates only design.md] + confirmation prompt
User: continue
AI: [Creates only tasks.md] + confirmation prompt
What ships with it
19 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.
- .gitignore 359 B
- CONTRIBUTING.md 4.9 KB
- LICENSE 1.0 KB
- README.md 6.9 KB
- references/ears-format.md 6.5 KB
- references/examples/feature-example.md 8.6 KB
- references/task-decomposition.md 7.3 KB
- references/workflow.md 7.2 KB
- scripts/execute-task.sh 9.3 KB runs code
- scripts/init-spec-flow.sh 5.2 KB runs code
- scripts/validate-spec-flow.py 11 KB runs code
- templates/design.md.template 4.4 KB
- templates/proposal.md.template 1.9 KB
- templates/requirements.md.template 3.5 KB
- templates/steering/constitution.md.template 2.2 KB
- templates/steering/product.md.template 2.2 KB
- templates/steering/structure.md.template 4.1 KB
- templates/steering/tech.md.template 3.2 KB
- templates/tasks.md.template 4.9 KB
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.
- 7d ago First seen · 394 lines · 61 tokens per session scan A 97e332e8f0eb
spec-flow is a skill published in the GitHub repository medalsoftchina/workcopilot (4 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 61 tokens to every session and 3,120 once invoked, about $0.0003 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-31.
Other skills, from other repositories
architecture-diagram
Build interactive, click-through architecture diagrams for software systems — a self-contained single HTML file with animated step-by-step flows, mode toggles (dev/prod, offline/online, v1/v2), dark/light theme, and a side panel with payload details, plus a companion markdown description. Use when the user wants to…
issue-authoring
Draft or refine IDD-ready GitHub issues, roadmap issues, and sub-issues before the normal IDD execution loop begins. Use when a request is too large or ambiguous for one reviewable change, when work needs decomposition or dependency encoding, or when the user asks for issue drafting, roadmap planning, or…
routeros-mac-telnet
MAC-Telnet protocol (MikroTik Layer-2 terminal/exec over UDP 20561) wire format, session handshake, and MD5 + MTWEI (EC-SRP) authentication. Use when: implementing or debugging a MAC-Telnet client/server, reaching a RouterOS device by MAC address without IP, parsing MAC-Telnet packets, understanding the WinBox-style…
routeros-qemu-chr
MikroTik RouterOS CHR (Cloud Hosted Router) with QEMU. Use when: running RouterOS in QEMU, booting CHR images, debugging CHR boot failures, setting up VirtIO devices for RouterOS, choosing between SeaBIOS and UEFI boot, configuring QEMU port forwarding for RouterOS REST API, setting up inter-VM socket networking or…
routeros-command-tree
RouterOS command tree introspection via /console/inspect API. Use when: building tools that parse RouterOS commands, generating API schemas from RouterOS, working with /console/inspect, mapping CLI commands to REST verbs, traversing the RouterOS command hierarchy, or when the user mentions inspect, command tree, RAML…
routeros-container
RouterOS /container subsystem for running OCI containers on MikroTik devices. Use when: enabling containers on RouterOS, setting up VETH/bridge networking for containers, managing container lifecycle via CLI or REST API, building OCI images for RouterOS, configuring container environment variables, troubleshooting…