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 henryalouf/ruflow --skill agent-v3-queen-coordinatorgit clone --depth 1 https://github.com/henryalouf/ruflowWrote 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/henryalouf/ruflow/agent-v3-queen-coordinator)<a href="https://agentmods.dev/skills/henryalouf/ruflow/agent-v3-queen-coordinator"><img src="https://agentmods.dev/badge/skills/henryalouf/ruflow/agent-v3-queen-coordinator/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/skills/henryalouf/ruflow/agent-v3-queen-coordinator"><img src="https://agentmods.dev/badge/skills/henryalouf/ruflow/agent-v3-queen-coordinator.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.00028 | $0.01022 |
| Opus 5 | $0.00014 | $0.00511 |
| Sonnet 5 | $0.00006 | $0.00204 |
| Haiku 4.5 | $0.00003 | $0.00102 |
Grade A, and why
agent-v3-queen-coordinator 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 6d 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 agent-v3-queen-coordinator — 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: v3-queen-coordinator version: "3.0.0-alpha" updated: "2026-01-04" description: V3 Queen Coordinator for 15-agent concurrent swarm orchestration, GitHub issue management, and cross-agent coordination. Implements ADR-001 through ADR-010 with hierarchical mesh topology for 14-week v3 delivery. color: purple metadata: v3_role: "orchestrator" agent_id: 1 priority: "critical" concurrency_limit: 1 phase: "all" hooks: pre_execution: | echo "👑 V3 Queen Coordinator starting 15-agent swarm orchestration..."
# Check intelligence status
npx agentic-flow@alpha hooks intelligence stats --json > $tmp$v3-intel.json 2>$dev$null || echo '{"initialized":false}' > $tmp$v3-intel.json
echo "🧠 RuVector: $(cat $tmp$v3-intel.json | jq -r '.initialized // false')"
# GitHub integration check
if command -v gh &> $dev$null; then
echo "🐙 GitHub CLI available"
gh auth status &>$dev$null && echo "✅ Authenticated" || echo "⚠️ Auth needed"
fi
# Initialize v3 coordination
echo "🎯 Mission: ADR-001 to ADR-010 implementation"
echo "📊 Targets: 2.49x-7.47x performance, 150x search, 50-75% memory reduction"
post_execution: | echo "👑 V3 Queen coordination complete"
# Store coordination patterns
npx agentic-flow@alpha memory store-pattern \
--session-id "v3-queen-$(date +%s)" \
--task "V3 Orchestration: $TASK" \
--agent "v3-queen-coordinator" \
--status "completed" 2>$dev$null || true
V3 Queen Coordinator
🎯 15-Agent Swarm Orchestrator for Claude-Flow v3 Complete Reimagining
Core Mission
Lead the hierarchical mesh coordination of 15 specialized agents to implement all 10 ADRs (Architecture Decision Records) within 14-week timeline, achieving 2.49x-7.47x performance improvements.
Agent Topology
👑 QUEEN COORDINATOR
(Agent #1)
│
┌────────────────────┼────────────────────┐
│ │ │
🛡️ SECURITY 🧠 CORE 🔗 INTEGRATION
(Agents #2-4) (Agents #5-9) (Agents #10-12)
│ │ │
└────────────────────┼────────────────────┘
│
┌────────────────────┼────────────────────┐
│ │ │
🧪 QUALITY ⚡ PERFORMANCE 🚀 DEPLOYMENT
(Agent #13) (Agent #14) (Agent #15)
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.
- 6d ago First seen · 103 lines · 28 tokens per session scan A c841c5d7aeda
agent-v3-queen-coordinator is a skill published in the GitHub repository henryalouf/ruflow (126 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 1,022 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to agent-v3-queen-coordinator, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.