Ruflo is an execution and coordination layer for Claude Code and Codex that equips AI coding agents with tools, memory, control loops, sandboxes, and collaboration mechanisms. Developers use it to organize specialized agents into swarms, coordinate workflows, retain knowledge across sessions, and communicate across machines. The catalogue entries are Ruflo’s skills, commands, agents, hooks, and plugin components.
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 skills/ruvnet/ruflo/worker-benchmarksnpx skills add ruvnet/ruflo --skill worker-benchmarksgit clone --depth 1 https://github.com/ruvnet/rufloWrote 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/ruvnet/ruflo/worker-benchmarks)<a href="https://agentmods.dev/skills/ruvnet/ruflo/worker-benchmarks"><img src="https://agentmods.dev/badge/skills/ruvnet/ruflo/worker-benchmarks.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.00013 | $0.00956 |
| Opus 5 | $0.00006 | $0.00478 |
| Sonnet 5 | $0.00003 | $0.00191 |
| Haiku 4.5 | $0.00001 | $0.00096 |
Grade A, and why
worker-benchmarks 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- worker-benchmarks — 100% identical, 0 lines differ
- worker-benchmarks — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Worker Benchmarks Skill
Run comprehensive performance benchmarks for the agentic-flow worker system.
Quick Start
# Run full benchmark suite
npx agentic-flow workers benchmark
# Run specific benchmark
npx agentic-flow workers benchmark --type trigger-detection
npx agentic-flow workers benchmark --type registry
npx agentic-flow workers benchmark --type agent-selection
npx agentic-flow workers benchmark --type concurrent
Benchmark Types
1. Trigger Detection (trigger-detection)
Tests keyword detection speed across 12 worker triggers.
- Target: p95 < 5ms
- Iterations: 1000
- Metrics: latency, throughput, histogram
2. Worker Registry (registry)
Tests CRUD operations on worker entries.
- Target: p95 < 10ms
- Iterations: 500 creates, gets, updates
- Metrics: per-operation latency breakdown
3. Agent Selection (agent-selection)
Tests performance-based agent selection.
- Target: p95 < 1ms
- Iterations: 1000
- Metrics: selection confidence, agent scores
4. Model Cache (cache)
Tests model caching performance.
- Target: p95 < 0.5ms
- Metrics: hit rate, cache size, eviction stats
5. Concurrent Workers (concurrent)
Tests parallel worker creation and updates.
- Target: < 1000ms for 10 workers
- Metrics: per-worker latency, memory usage
6. Memory Key Generation (memory-keys)
Tests memory pattern key generation.
- Target: p95 < 0.1ms
- Iterations: 5000
- Metrics: unique patterns, throughput
Output Format
═══════════════════════════════════════════════════════════
📈 BENCHMARK RESULTS
═══════════════════════════════════════════════════════════
✅ Trigger Detection
Operation: detect
Count: 1,000
Avg: 0.045ms | p95: 0.120ms (target: 5ms)
Throughput: 22,222 ops$s
Memory Δ: 0.12MB
✅ Worker Registry
Operation: crud
Count: 1,500
Avg: 1.234ms | p95: 3.456ms (target: 10ms)
Throughput: 810 ops$s
Memory Δ: 2.34MB
───────────────────────────────────────────────────────────
📊 SUMMARY
───────────────────────────────────────────────────────────
Total Tests: 6
Passed: 6 | Failed: 0
Avg Latency: 0.567ms
Total Duration: 2345ms
Peak Memory: 8.90MB
═══════════════════════════════════════════════════════════
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 · 136 lines · 13 tokens per session scan A f1a8d511da98
worker-benchmarks is a skill published in the GitHub repository ruvnet/ruflo (70,334 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 956 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
image-generation
Use this skill when the user requests to generate, create, imagine, or visualize images including characters, scenes, products, or any visual content. Supports structured prompts and reference images for guided generation.
example-safe-skill
Reviews a single Markdown troubleshooting note for clarity. Invoke when the user asks to improve a provided troubleshooting note.
nw-design
Designs system architecture with C4 diagrams and technology selection. Routes to the right architect based on design scope (system, domain, application, or full stack). Two interaction modes: guide (collaborative Q&A) or propose (architect presents options with trade-offs).
nw-ddd-eventsourcing
Event Sourcing and CQRS as DDD implementation patterns — when to use, aggregate event streams, projections, snapshots, sagas, upcasting, conflict resolution.
nw-fp-algebra-driven-design
Algebra-driven API design with monoids, semigroups, and interpreters via algebraic equations.
nw-research
Gathers knowledge from web and files, cross-references across multiple sources, and produces cited research documents. Use when investigating technologies, patterns, or decisions that need evidence backing.