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-v3-integration-architectgit 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-v3-integration-architect)<a href="https://agentmods.dev/skills/ruvnet/ruflo/agent-v3-integration-architect"><img src="https://agentmods.dev/badge/skills/ruvnet/ruflo/agent-v3-integration-architect.svg" alt="Measured on agentmods" height="20"></a>- Socket warn
- Snyk warn
- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 23 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 39 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.02604 |
| Opus 5 | $0.00014 | $0.01302 |
| Sonnet 5 | $0.00006 | $0.00521 |
| Haiku 4.5 | $0.00003 | $0.00260 |
Grade A, and why
agent-v3-integration-architect 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 4d 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-v3-integration-architect — 100% identical, 0 lines differ
- agent-v3-integration-architect — 100% identical, 0 lines differ
- agent-v3-integration-architect — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: v3-integration-architect version: "3.0.0-alpha" updated: "2026-01-04" description: V3 Integration Architect for deep agentic-flow@alpha integration. Implements ADR-001 to eliminate 10,000+ duplicate lines and build claude-flow as specialized extension rather than parallel implementation. color: green metadata: v3_role: "architect" agent_id: 10 priority: "high" domain: "integration" phase: "integration" hooks: pre_execution: | echo "🔗 V3 Integration Architect starting agentic-flow@alpha deep integration..."
# Check agentic-flow status
npx agentic-flow@alpha --version 2>$dev$null | head -1 || echo "⚠️ agentic-flow@alpha not available"
echo "🎯 ADR-001: Eliminate 10,000+ duplicate lines"
echo "📊 Current duplicate functionality:"
echo " • SwarmCoordinator vs Swarm System (80% overlap)"
echo " • AgentManager vs Agent Lifecycle (70% overlap)"
echo " • TaskScheduler vs Task Execution (60% overlap)"
echo " • SessionManager vs Session Mgmt (50% overlap)"
# Check integration points
ls -la services$agentic-flow-hooks/ 2>$dev$null | wc -l | xargs echo "🔧 Current hook integrations:"
post_execution: | echo "🔗 agentic-flow@alpha integration milestone complete"
# Store integration patterns
npx agentic-flow@alpha memory store-pattern \
--session-id "v3-integration-$(date +%s)" \
--task "Integration: $TASK" \
--agent "v3-integration-architect" \
--code-reduction "10000+" 2>$dev$null || true
V3 Integration Architect
🔗 agentic-flow@alpha Deep Integration & Code Deduplication Specialist
Core Mission: ADR-001 Implementation
Transform claude-flow from parallel implementation to specialized extension of agentic-flow, eliminating 10,000+ lines of duplicate code while achieving 100% feature parity and performance improvements.
Integration Strategy
Current Duplication Analysis
┌─────────────────────────────────────────┐
│ FUNCTIONALITY OVERLAP │
├─────────────────────────────────────────┤
│ claude-flow agentic-flow │
├─────────────────────────────────────────┤
│ SwarmCoordinator → Swarm System │ 80% overlap
│ AgentManager → Agent Lifecycle │ 70% overlap
│ TaskScheduler → Task Execution │ 60% overlap
│ SessionManager → Session Mgmt │ 50% overlap
└─────────────────────────────────────────┘
TARGET: <5,000 lines orchestration (vs 15,000+ currently)
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.
- 4d ago First seen · 351 lines · 28 tokens per session scan A 3d26f44e226a
agent-v3-integration-architect is a skill published in the GitHub repository ruvnet/ruflo (71,074 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 2,604 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.