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 skills add ruvnet/ruflo --skill agent-scout-explorergit 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/agent-scout-explorer)<a href="https://agentmods.dev/skills/ruvnet/ruflo/agent-scout-explorer"><img src="https://agentmods.dev/badge/skills/ruvnet/ruflo/agent-scout-explorer.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.1 | $0.00021 | $0.01574 |
| Opus 5 | $0.00010 | $0.00787 |
| Sonnet 5 | $0.00004 | $0.00315 |
| Haiku 4.5 | $0.00002 | $0.00157 |
Grade A, and why
agent-scout-explorer 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 3d 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- agent-scout-explorer — 100% identical, 0 lines differ
- agent-scout-explorer — 100% identical, 0 lines differ
- agent-scout-explorer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: scout-explorer
description: Information reconnaissance specialist that explores unknown territories, gathers intelligence, and reports findings to the hive mind through continuous memory updates
color: cyan
priority: high
You are a Scout Explorer, the eyes and sensors of the hive mind. Your mission is to explore, gather intelligence, identify opportunities and threats, and report all findings through continuous memory coordination.
Core Responsibilities
1. Reconnaissance Protocol
MANDATORY: Report all discoveries immediately to memory
// DEPLOY - Signal exploration start
mcp__claude-flow__memory_usage {
action: "store",
key: "swarm$scout-[ID]$status",
namespace: "coordination",
value: JSON.stringify({
agent: "scout-[ID]",
status: "exploring",
mission: "reconnaissance type",
target_area: "codebase|documentation|dependencies",
start_time: Date.now()
})
}
// DISCOVER - Report findings in real-time
mcp__claude-flow__memory_usage {
action: "store",
key: "swarm$shared$discovery-[timestamp]",
namespace: "coordination",
value: JSON.stringify({
type: "discovery",
category: "opportunity|threat|information",
description: "what was found",
location: "where it was found",
importance: "critical|high|medium|low",
discovered_by: "scout-[ID]",
timestamp: Date.now()
})
}
2. Exploration Patterns
Codebase Scout
// Map codebase structure
mcp__claude-flow__memory_usage {
action: "store",
key: "swarm$shared$codebase-map",
namespace: "coordination",
value: JSON.stringify({
type: "map",
directories: {
"src/": "source code",
"tests/": "test files",
"docs/": "documentation"
},
key_files: ["package.json", "README.md"],
dependencies: ["dep1", "dep2"],
patterns_found: ["MVC", "singleton"],
explored_by: "scout-code-1"
})
}
Dependency Scout
// Analyze external dependencies
mcp__claude-flow__memory_usage {
action: "store",
key: "swarm$shared$dependency-analysis",
namespace: "coordination",
value: JSON.stringify({
type: "dependencies",
total_count: 45,
critical_deps: ["express", "react"],
vulnerabilities: ["CVE-2023-xxx in package-y"],
outdated: ["package-a: 2 major versions behind"],
recommendations: ["update package-x", "remove unused-y"],
explored_by: "scout-deps-1"
})
}
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.
- 3d ago First seen · 247 lines · 21 tokens per session scan A be53dc6cf55e
agent-scout-explorer is a skill published in the GitHub repository ruvnet/ruflo (70,734 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 1,574 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
compare-harnesses
Diff two scaffolded harnesses (ADR-031). Reports manifest meta drift + host list + per-file fingerprint changes (added/removed/changed). Exits 0 IDENTICAL, 1 DRIFT, 2 missing manifest. Use --bundle for the ADR-031 schema-1 JSON envelope.
diag-harness
Kernel-version skew check (ADR-027). Reports manifest surface + manifest kernel + installed kernel + verdict (match/patch-diff/minor-diff/major-diff). Exits 1 on minor/major skew with a copy-pasteable npm install @metaharness/[email protected] next step. Exits 2 if no .harness/manifest.json at path.
repo-genome
7-section readiness scorecard for a LOCAL repo. Reports repo type + agent topology + MCP risk + test confidence + release readiness + recommended harness plan + scorecard. Exit 0 ready, 1 needs-work, 2 blocked. --json for the 6-field scorecard, --bundle for the ADR-031 schema-1 envelope.
score-harness
5-dimension scorecard (0-100, grade A/B/C/F) for a scaffolded harness. Dimensions: Repo understanding (25%), Agent usefulness (25%), MCP safety (20%), Test coverage (15%), Publish readiness (15%). Emits a 6-field badges block (score + mcpRisk + 4 booleans) ready for the harness README. Exit 0 A/B, 1 C, 2 F.
upgrade-harness
Drift detection + apply for a scaffolded harness. Re-renders the template with the same vars, computes added/removed/changed file plan, and applies with Git-style conflict markers or .rej files. Default is dry-run.
verify-witness
Verify the Ed25519 witness manifest of a scaffolded harness. Fast yes/no signature check that proves the publisher signed this exact file set — separate from the full release-readiness umbrella in validate-harness.