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/ruvnet/ruv-FANNWrote 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/ruvnet/ruv-fann/workflow-execute)<a href="https://agentmods.dev/commands/ruvnet/ruv-fann/workflow-execute"><img src="https://agentmods.dev/badge/commands/ruvnet/ruv-fann/workflow-execute/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/ruvnet/ruv-fann/workflow-execute"><img src="https://agentmods.dev/badge/commands/ruvnet/ruv-fann/workflow-execute.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.00135 |
| Opus 5.5 | $0.00000 | $0.00054 |
| Sonnet 5.5 | $0.00000 | $0.00027 |
| Haiku 4.5 | $0.00000 | $0.00014 |
Grade A, and why
workflow-execute 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-execute — 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-execute
Execute saved workflows.
Usage
npx claude-flow workflow execute [options]
Options
--name <name>- Workflow name--params <json>- Workflow parameters--dry-run- Preview execution
Examples
# Execute workflow
npx claude-flow workflow execute --name "deploy-api"
# With parameters
npx claude-flow workflow execute --name "test-suite" --params '{"env": "staging"}'
# Dry run
npx claude-flow workflow execute --name "deploy-api" --dry-run
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 fc86e679840c
workflow-execute is a command published in the GitHub repository ruvnet/ruv-FANN (387 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 135 tokens. A static security scan graded it A with 0 findings. It is 100% identical to workflow-execute, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
project-groups
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
sddp-devops
Command description: Create or refine the deployment and operations document. Argument hint: [project description, infrastructure context, deployment constraints, or operations inputs] Command category: project-bootstrap Prerequisites: none.
migrating-fabric-trial-capacities
Migrate workspaces from trial capacity to production capacity.
jira-issue-use-aws
Same as /jira-issue, plus an AWS deep-dive — diagnose the reported symptom through the operator's live AWS CLI session using strictly read-only calls (logs, metrics, resource state, CloudTrail) before filing the groomed Jira issue with cloud-traced evidence. Example — /jira-issue-use-aws "file export" presigned…
lock
Hold a shared resource (deploy, migration, environment) for a while.
cycle
Execute continuous development cycle for an epic.