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 skills/proffesor-for-testing/agentic-qe/agent-paymentsnpx skills add proffesor-for-testing/agentic-qe --skill agent-paymentsgit clone --depth 1 https://github.com/proffesor-for-testing/agentic-qeWrote 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/proffesor-for-testing/agentic-qe/agent-payments)<a href="https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/agent-payments"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/agent-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.1 | $0.00015 | $0.00769 |
| Opus 5 | $0.00008 | $0.00385 |
| Sonnet 5 | $0.00003 | $0.00154 |
| Haiku 4.5 | $0.00002 | $0.00077 |
Grade A, and why
agent-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 6d 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 agent-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.
What it actually says
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.
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.
- 6d ago First seen · 88 lines · 15 tokens per session scan A f077218d3566
agent-payments is a skill published in the GitHub repository proffesor-for-testing/agentic-qe (474 stars, last pushed 3d ago), licensed MIT. It adds 15 tokens to every session and 769 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 agent-payments, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
risk-scoring
Score how concentrated and risky a portfolio is on a 0-100 scale from its position weights. Use when the user asks how risky their portfolio is, whether it is too concentrated, or for a diversification check.
cost-efficiency-analyzer
Analyzes cost structure, cost efficiency, and expense management from P&L data. Use when the user asks about costs, expenses, COGS, operating expenses, cost ratios, cost control, spending efficiency, margin compression from cost side, or wants to understand where money is going. Also use for "are we spending too…
sector-rotation
Identify which market sectors to overweight or underweight based on current macro conditions and sector performance data.
trend-analysis
Analyze price and volume trends for one or more stocks to determine momentum direction and key technical levels.
azure-cost
Azure cost management: query costs, forecast spending, optimize to reduce waste. WHEN: "Azure costs", "Azure bill", "cost breakdown", "how much am I spending", "forecast spending", "optimize costs", "reduce spending", "orphaned resources", "rightsize VMs", "cost spike", "reduce storage costs", "AKS cost". DO NOT USE…
picks-tracker
Retrospective on past token and prediction market picks - what hit, what flopped, what the score is.