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/soulcynics404/agentforge/task-orchestrategit clone --depth 1 https://github.com/Soulcynics404/AgentForgeWrote 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/soulcynics404/agentforge/task-orchestrate)<a href="https://agentmods.dev/commands/soulcynics404/agentforge/task-orchestrate"><img src="https://agentmods.dev/badge/commands/soulcynics404/agentforge/task-orchestrate.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.00159 |
| Opus 5 | $0.00000 | $0.00079 |
| Sonnet 5 | $0.00000 | $0.00032 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
task-orchestrate 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 task-orchestrate — 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
task-orchestrate
Orchestrate complex tasks across the swarm.
Usage
npx claude-flow task orchestrate [options]
Options
--task <description>- Task description--strategy <type>- Orchestration strategy--priority <level>- Task priority (low, medium, high, critical)
Examples
# Orchestrate development task
npx claude-flow task orchestrate --task "Implement user authentication"
# High priority task
npx claude-flow task orchestrate --task "Fix production bug" --priority critical
# With specific strategy
npx claude-flow task orchestrate --task "Refactor codebase" --strategy parallel
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 · 26 lines · 0 tokens per session scan A 900ea2e5024c
task-orchestrate is a command published in the GitHub repository Soulcynics404/AgentForge (1 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 159 tokens. A static security scan graded it A with 0 findings. It is 100% identical to task-orchestrate, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
agentos-status
Show AgentOS system status — agents, workers, health.
agentos-tui
Launch the AgentOS TUI dashboard.
agentos-evolve
Quick evolve a function — generate, register, and evaluate.
agentos-chat
Send a message to an AgentOS agent.
agentos-orchestrate
Quick orchestrate a feature — decompose, plan, and execute.
specsync-create-spec
Create a new spec-sync module spec.