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/airmcp-com/mcp-standardsWrote 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/airmcp-com/mcp-standards/workflow-create)<a href="https://agentmods.dev/commands/airmcp-com/mcp-standards/workflow-create"><img src="https://agentmods.dev/badge/commands/airmcp-com/mcp-standards/workflow-create/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/airmcp-com/mcp-standards/workflow-create"><img src="https://agentmods.dev/badge/commands/airmcp-com/mcp-standards/workflow-create.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.00000 | $0.00121 |
| Opus 5.5 | $0.00000 | $0.00048 |
| Sonnet 5.5 | $0.00000 | $0.00024 |
| Haiku 4.5 | $0.00000 | $0.00012 |
Grade A, and why
workflow-create 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.
This is a copy
100% identical to workflow-create — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
workflow-create
Create reusable workflow templates.
Usage
npx claude-flow workflow create [options]
Options
--name <name>- Workflow name--from-history- Create from history--interactive- Interactive creation
Examples
# Create workflow
npx claude-flow workflow create --name "deploy-api"
# From history
npx claude-flow workflow create --name "test-suite" --from-history
# Interactive mode
npx claude-flow workflow create --interactive
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 · 26 lines · 0 tokens per session scan A baf1e6c2a2de
workflow-create is a command published in the GitHub repository airmcp-com/mcp-standards (3 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 121 tokens. A static security scan graded it A with 0 findings. It is 100% identical to workflow-create, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
triage
Triage and categorize findings for the CLI todo system.
resolve_todo_parallel
Resolve all pending CLI todos using parallel processing.
backlog
The project layer: milestones, epics, and user stories with refusing controllers — spec-seeded, sprint-ready.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
sdd
A command that creates three connected planning files for a software feature: requirements, design, and tasks.
team
A team workflow command that splits one task into parallel tracks while keeping their work in a shared project tree. It assigns roles, records reports and locks, and coordinates scoped commits through a central board.