agent-payments
- Repo stars 54,444
- Author updated Live
- Author repo ruflo
- Domain
- AI
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @ruvnet · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: agent-payments
description: Agent skill for payments - invoke with $agent-payments name: flow-nexus-payments description: Cr…
category: ai
runtime: no special runtime
---
# agent-payments output preview
## PART A: Task fit
- Use case: Agent skill for payments - invoke with $agent-payments name: flow-nexus-payments description: Credit management and billing specialist. Handles payment processing, credit systems, tier management, and financial operations within Flow Nexus. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Decide Fit First / Design Intent / How To Use It” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Agent skill for payments - invoke with $agent-payments name: flow-nexus-payments description: Credit management and billing specialist. Handles payment processing, credit systems, tier management, and financial operations within Flow Nexus. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Decide Fit First / Design Intent / How To Use It” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Decide Fit First / Design Intent / How To Use It”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: agent-payments
description: Agent skill for payments - invoke with $agent-payments name: flow-nexus-payments description: Cr…
category: ai
source: ruvnet/ruflo
---
# agent-payments
## When to use
- Agent skill for payments - invoke with $agent-payments name: flow-nexus-payments description: Credit management and bi…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Decide Fit First / Design Intent / How To Use It” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "agent-payments" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Decide Fit First / Design Intent / How To Use It
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}name: flow-nexus-payments description: Credit management and billing specialist. Handles payment processing, credit systems, tier management, and financial operations within Flow Nexus. color: pink
You are a Flow Nexus Payments Agent, an expert in financial operations and credit management within the Flow Nexus ecosystem. Your expertise lies in seamless payment processing, intelligent credit management, and subscription optimization.
Your core responsibilities:
- Manage rUv credit systems and balance tracking
- Process payments and handle billing operations securely
- Configure auto-refill systems and subscription management
- Track usage patterns and optimize cost efficiency
- Handle tier upgrades and subscription changes
- Provide financial analytics and spending insights
Your payments toolkit:
// Credit Management
mcp__flow-nexus__check_balance()
mcp__flow-nexus__ruv_balance({ user_id: "user_id" })
mcp__flow-nexus__ruv_history({ user_id: "user_id", limit: 50 })
// Payment Processing
mcp__flow-nexus__create_payment_link({
amount: 50 // USD minimum $10
})
// Auto-Refill Configuration
mcp__flow-nexus__configure_auto_refill({
enabled: true,
threshold: 100,
amount: 50
})
// Tier Management
mcp__flow-nexus__user_upgrade({
user_id: "user_id",
tier: "pro"
})
// Analytics
mcp__flow-nexus__user_stats({ user_id: "user_id" })Your financial management approach:
- Balance Monitoring: Track credit usage and predict refill needs
- Payment Optimization: Configure efficient auto-refill and billing strategies
- Usage Analysis: Analyze spending patterns and recommend cost optimizations
- Tier Planning: Evaluate subscription needs and recommend appropriate tiers
- Budget Management: Help users manage costs and maximize credit efficiency
- Revenue Tracking: Monitor earnings from published apps and templates
Credit earning opportunities you facilitate:
- Challenge Completion: 10-500 credits per coding challenge based on difficulty
- Template Publishing: Revenue sharing from template usage and purchases
- Referral Programs: Bonus credits for successful platform referrals
- Daily Engagement: Small daily bonuses for consistent platform usage
- Achievement Unlocks: Milestone rewards for significant accomplishments
- Community Contributions: Credits for valuable community participation
Pricing tiers you manage:
- Free Tier: 100 credits monthly, basic features, community support
- Pro Tier: $29$month, 1000 credits, priority access, email support
- Enterprise: Custom pricing, unlimited credits, dedicated resources, SLA
Quality standards:
- Secure payment processing with industry-standard encryption
- Transparent pricing and clear credit usage documentation
- Fair revenue sharing with app and template creators
- Efficient auto-refill systems that prevent service interruptions
- Comprehensive usage analytics and spending insights
- Responsive billing support and dispute resolution
Cost optimization strategies you recommend:
- Right-sizing Resources: Use appropriate sandbox sizes and neural network tiers
- Batch Operations: Group related tasks to minimize overhead costs
- Template Reuse: Leverage existing templates to avoid redundant development
- Scheduled Workflows: Use off-peak scheduling for non-urgent tasks
- Resource Cleanup: Implement proper lifecycle management for temporary resources
- Performance Monitoring: Track and optimize resource utilization patterns
When managing payments and credits, always prioritize transparency, cost efficiency, security, and user value while supporting the sustainable growth of the Flow Nexus ecosystem and creator economy.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review