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.
git 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/commands/ruvnet/ruflo/app-store)<a href="https://agentmods.dev/commands/ruvnet/ruflo/app-store"><img src="https://agentmods.dev/badge/commands/ruvnet/ruflo/app-store/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/commands/ruvnet/ruflo/app-store"><img src="https://agentmods.dev/badge/commands/ruvnet/ruflo/app-store.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.00013 | $0.00706 |
| Opus 5.5 | $0.00005 | $0.00282 |
| Sonnet 5.5 | $0.00003 | $0.00141 |
| Haiku 4.5 | $0.00001 | $0.00071 |
Grade A, and why
flow-nexus-app-store 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 1mo 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
8 near-identical copies found in the catalogue:
- flow-nexus-app-store — 100% identical, 128 lines differ
- flow-nexus-app-store — 100% identical, 0 lines differ
- flow-nexus-app-store — 100% identical, 0 lines differ
- flow-nexus-app-store — 100% identical, 0 lines differ
- flow-nexus-app-store — 100% identical, 0 lines differ
- flow-nexus-app-store — 100% identical, 0 lines differ
- flow-nexus-app-store — 100% identical, 0 lines differ
- flow-nexus-app-store — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flow Nexus App Store
Browse templates, publish apps, and deploy solutions.
Browse Apps
// Search apps
mcp__flow-nexus__app_search({
search: "authentication",
category: "backend",
featured: true,
limit: 20
})
// Get app details
mcp__flow-nexus__app_get({ app_id: "app_id" })
// List templates
mcp__flow-nexus__app_store_list_templates({
category: "web-api",
tags: ["express", "jwt"],
limit: 20
})
Publish App
mcp__flow-nexus__app_store_publish_app({
name: "My Auth Service",
description: "JWT-based authentication microservice",
category: "backend",
version: "1.0.0",
source_code: sourceCode,
tags: ["auth", "jwt", "express"],
metadata: {
author: "Your Name",
license: "MIT",
repository: "github.com/user/repo"
}
})
Deploy Templates
// Get template details
mcp__flow-nexus__template_get({
template_name: "express-api-starter"
})
// Deploy template
mcp__flow-nexus__template_deploy({
template_name: "express-api-starter",
deployment_name: "my-api",
variables: {
api_key: "your_key",
database_url: "postgres://..."
},
env_vars: {
NODE_ENV: "production"
}
})
Analytics
// Get app analytics
mcp__flow-nexus__app_analytics({
app_id: "your_app_id",
timeframe: "30d" // 24h, 7d, 30d, 90d
})
// View installed apps
mcp__flow-nexus__app_installed({
user_id: "your_id"
})
Update App
mcp__flow-nexus__app_update({
app_id: "app_id",
updates: {
version: "1.1.0",
description: "Updated description",
tags: ["new", "tags"]
}
})
Market Data
// Get market statistics
mcp__flow-nexus__market_data()
Template Categories
- web-api: RESTful APIs and microservices
- frontend: React, Vue, Angular apps
- full-stack: Complete applications
- cli-tools: Command-line utilities
- data-processing: ETL and analytics
- ml-models: Pre-trained models
- blockchain: Web3 applications
- mobile: React Native apps
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.
- 1mo ago First seen · 124 lines · 13 tokens per session scan A 0faef1c336db
flow-nexus-app-store is a command published in the GitHub repository ruvnet/ruflo (77,829 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 706 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
api-documentation
Generate comprehensive API documentation for FastAPI endpoints.
legal-5step
Execute the BetterCallClaude 5-step Swiss legal framework: intake → research → strategy → adversarial → draft. A complete end-to-end pipeline for any Swiss legal matter, from document analysis through final legal output.
start
Welcome and first-use onboarding — checks MCP connectivity, guides playbook creation, shows usage examples tailored to your profile. Replaces /setup.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.