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 commands/natea/exomind/paymentsgit clone --depth 1 https://github.com/natea/ExoMindWrote 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/natea/exomind/payments)<a href="https://agentmods.dev/commands/natea/exomind/payments"><img src="https://agentmods.dev/badge/commands/natea/exomind/payments.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.00014 | $0.00632 |
| Opus 5 | $0.00007 | $0.00316 |
| Sonnet 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 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.
This is a copy
100% identical to flow-nexus-payments — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 3d ago First seen · 116 lines · 14 tokens per session scan A 194f0132c800
flow-nexus-payments is a command published in the GitHub repository natea/ExoMind (21 stars, last pushed 10mo ago), licensed MIT. It adds 14 tokens to every session and 632 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to flow-nexus-payments, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
merit-reconcile
Preview or check the status of Stripe → Merit payout reconciliation (read-only).
valuation-methods
Valuation methods analysis — multiples, DCF inputs, PEG integration, valuation assumption extraction.
scan
Scan AWS account for cost optimization.
audit-checklist
Perform an internal audit, review controls, or prepare for an external financial audit.
finops-status
Orientation — say where an opportunity or assignment sits in the five-step FinOps lifecycle and what unlocks next. Useful when a record has no active stage: an opportunity while its assignments do the work, an assignment whose plan has not been approved yet, or a rejected or archived assignment. Read-only; mutates…