agent-payments

agent-payments is a skill for Claude Code from proffesor-for-testing/agentic-qe. It costs 15 tokens per session (769 once invoked), scanned A, a copy of agent-payments, MIT.

A specialist workflow for managing payments, credits, subscriptions, billing, and related financial operations in the Flow Nexus system. It includes responsibilities such as balance tracking, payment processing, and tier changes.

In plain words
What is it for?
Use it for checking balances, processing payments, configuring automatic credit refills, reviewing usage, changing subscription tiers, and financial reporting.
Why use it?
It gives financial tasks a dedicated place and keeps credit usage, payments, and subscription changes organized. The input does not describe a broader purpose beyond Flow Nexus financial operations.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: installed under .agents/ (shared by several agents); $skill-name invocation.

Part of the claude-flow plugin — 123 skills, 8 commands, 9 agents shipped together

Good fit Use it for checking balances, processing payments, configuring automatic credit refills, reviewing usage, changing subscription tiers, and financial reporting.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/proffesor-for-testing/agentic-qe/agent-payments
Install

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.

Any agent
npx skills add proffesor-for-testing/agentic-qe --skill agent-payments
Clone the repo
git clone --depth 1 https://github.com/proffesor-for-testing/agentic-qe

Made for: Claude Code.

Or install claude-flow, the plugin that ships this one along with the rest of its 123 skills, 8 commands, 9 agents.

Wrote 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.

agentmods badge for agent-payments

README.md
[![agentmods](https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/agent-payments/github.svg)](https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/agent-payments)
Your own site
<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/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.

agentmods 80×15 button for agent-payments

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 769 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00015 $0.00769
Opus 5.5 $0.00006 $0.00308
Sonnet 5.5 $0.00003 $0.00154
Haiku 4.5 $0.00002 $0.00077

Measured 1mo ago against content hash f077218d3566, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

Origin

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.

.agents/skills/ruflo/.agents/skills/agent-payments/SKILL.md · 88 lines

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:

  1. Balance Monitoring: Track credit usage and predict refill needs
  2. Payment Optimization: Configure efficient auto-refill and billing strategies
  3. Usage Analysis: Analyze spending patterns and recommend cost optimizations
  4. Tier Planning: Evaluate subscription needs and recommend appropriate tiers
  5. Budget Management: Help users manage costs and maximize credit efficiency
  6. 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.

Changes

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.

  1. 1mo ago First seen · 88 lines · 15 tokens per session scan A f077218d3566

Subscribe to this mod's changes

agent-payments is a skill published in the GitHub repository proffesor-for-testing/agentic-qe (512 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 769 once invoked, about $0.0001 per session on Opus 5.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.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens