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 agentmods add commands/ruvnet/sublinear-time-solver/workflow-managergit clone --depth 1 https://github.com/ruvnet/sublinear-time-solverWrote 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/sublinear-time-solver/workflow-manager)<a href="https://agentmods.dev/commands/ruvnet/sublinear-time-solver/workflow-manager"><img src="https://agentmods.dev/badge/commands/ruvnet/sublinear-time-solver/workflow-manager.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 | $0.00000 | $0.00269 |
| Opus 5 | $0.00000 | $0.00134 |
| Sonnet 5 | $0.00000 | $0.00054 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
workflow-manager 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 yesterday.
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-manager — 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
SPARC Workflow Manager Mode
Purpose
Process automation with TodoWrite planning and Task execution.
Activation
Option 1: Using MCP Tools (Preferred in Claude Code)
mcp__claude-flow__sparc_mode {
mode: "workflow-manager",
task_description: "automate deployment",
options: {
pipeline: "ci-cd",
rollback_enabled: true
}
}
Option 2: Using NPX CLI (Fallback when MCP not available)
# Use when running from terminal or MCP tools unavailable
npx claude-flow sparc run workflow-manager "automate deployment"
# For alpha features
npx claude-flow@alpha sparc run workflow-manager "automate deployment"
Option 3: Local Installation
# If claude-flow is installed locally
./claude-flow sparc run workflow-manager "automate deployment"
Core Capabilities
- Workflow design
- Process automation
- Pipeline creation
- Event handling
- State management
Workflow Patterns
- Sequential flows
- Parallel branches
- Conditional logic
- Loop iterations
- Error handling
Automation Features
- Trigger management
- Task scheduling
- Progress tracking
- Result validation
- Rollback capability
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.
- yesterday First seen · 55 lines · 0 tokens per session scan A 446e60777a5d
workflow-manager is a command published in the GitHub repository ruvnet/sublinear-time-solver (89 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 269 tokens. A static security scan graded it A with 0 findings. It is 100% identical to workflow-manager, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
access
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.
release
Cut a release — derive the version, close the review, rewrite CHANGELOG, commit, push, wait for CI, tag, wait for the Release workflow and the GitHub release, then wait until the version is live on NuGet.
start-11-4.es
Leccion 11-4: Llamar a AI CLI desde GitHub Actions!
ship
Deploy feature through automated staging validation to production with rollback testing.
ci-loop
Push code, wait for CI, parse failures, auto-fix, and iterate until green. Automated CI feedback loop.