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.
Borrowing it
Nothing to install: this file belongs to ruvnet/ruflo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ruvnet/ruflo/main/.claude/commands/flow-nexus/payments.mdgit 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/payments)<a href="https://agentmods.dev/commands/ruvnet/ruflo/payments"><img src="https://agentmods.dev/badge/commands/ruvnet/ruflo/payments/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/payments"><img src="https://agentmods.dev/badge/commands/ruvnet/ruflo/payments.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.00014 | $0.00632 |
| Opus 5.5 | $0.00006 | $0.00253 |
| Sonnet 5.5 | $0.00003 | $0.00126 |
| Haiku 4.5 | $0.00001 | $0.00063 |
Grade A, and why
flow-nexus-payments 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-payments — 100% identical, 0 lines differ
- flow-nexus-payments — 100% identical, 0 lines differ
- flow-nexus-payments — 100% identical, 0 lines differ
- flow-nexus-payments — 100% identical, 0 lines differ
- flow-nexus-payments — 100% identical, 0 lines differ
- flow-nexus-payments — 100% identical, 0 lines differ
- flow-nexus-payments — 100% identical, 0 lines differ
- flow-nexus-payments — 100% identical, 81 lines differ
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flow Nexus Payments
Manage credits, configure billing, and track usage.
Check Balance
mcp__flow-nexus__check_balance()
Purchase Credits
// Create payment link
mcp__flow-nexus__create_payment_link({
amount: 50 // USD, minimum $10
})
// Returns secure payment URL to complete purchase
Auto-Refill Configuration
// Enable auto-refill
mcp__flow-nexus__configure_auto_refill({
enabled: true,
threshold: 100, // Refill when credits drop below 100
amount: 50 // Refill with $50 worth of credits
})
// Disable auto-refill
mcp__flow-nexus__configure_auto_refill({
enabled: false
})
Payment History
mcp__flow-nexus__get_payment_history({
limit: 50
})
rUv Credits Management
// Check balance
mcp__flow-nexus__ruv_balance({
user_id: "your_id"
})
// Transaction history
mcp__flow-nexus__ruv_history({
user_id: "your_id",
limit: 100
})
Upgrade Tier
mcp__flow-nexus__user_upgrade({
user_id: "your_id",
tier: "pro" // pro, enterprise
})
Usage Statistics
mcp__flow-nexus__user_stats({
user_id: "your_id"
})
Credit Pricing
- Swarm Operations: 1-10 credits/hour
- Sandbox Execution: 0.5-5 credits/hour
- Neural Training: 5-50 credits/job
- Workflow Runs: 0.1-1 credit/execution
- Storage: 0.01 credits/GB/day
Earning Credits
- Complete Challenges: 10-500 credits per challenge
- Publish Templates: Earn when others use
- Referrals: Bonus credits for invites
- Daily Login: Small daily bonus
- Achievements: Unlock milestone rewards
Tiers
Free Tier
- 100 free credits monthly
- Basic sandbox access
- Limited swarm agents (3 max)
- Community support
Pro Tier ($29/month)
- 1000 credits monthly
- Priority sandbox access
- Unlimited agents
- Advanced workflows
- Email support
Enterprise Tier (Custom)
- Unlimited credits
- Dedicated resources
- Custom models
- SLA guarantee
- Priority support
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 · 116 lines · 14 tokens per session scan A 194f0132c800
flow-nexus-payments is a command published in the GitHub repository ruvnet/ruflo (77,172 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 632 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
briefing
Structured pre-execution briefing session -- collects case context through specialist panel, builds execution plan, supports resume and depth control.
help
Show complete BetterCallClaude command reference, available agents, skills, and usage examples.
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.
legal-goal
Define a checkable legal success condition for /legal-loop. Accepts a named profile (citations-clean, draft-passes-gate, adversarial-converge, nda-batch-clean, reg-watch, timeline-sourced) or free-text objective. Produces a persisted Goal Record — never starts work itself.
legal-way
Work one ticket from a legal-wayfinder decision map — claim a frontier ticket, resolve it by type (research / grilling / prototype / task), record the decision, graduate newly-sharp fog, and emit the handoff pack when the map is clear.
create-workflow
Create a reusable custom workflow by combining BetterCallClaude agents. Interview-based: pick agents, order them, define the output. Saved for future use with /bettercallclaude:workflow.