agent-agentic-payments
Skill1 starsChanged 7 months agoMITView on GitHub
Agent skill for agentic-payments - invoke with $agent-agentic-payments
5 other projects use a version of this, 5 of them edited.
Adopted by
Most recently taken up by
- ruvnet/rufloedited, first seen Oct 21, 2026
- ruvnet/claude-flowedited, first seen Oct 8, 2026
- Soulcynics404/AgentForgeedited, first seen Aug 24, 2026
- jpoindexter/theft-kitedited, first seen May 20, 2026
- Zekiog/rufloedited, first seen Apr 8, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 5
- ruvnet/claude-flow★ 80k99% same
- ruvnet/ruflo★ 79k99% same
- Zekiog/ruflo★ 299% same
- jpoindexter/theft-kit★ 199% same
- Soulcynics404/AgentForge★ 199% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository175 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/commands/monitoring/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- v2/CLAUDE.mdCLAUDE.md
- v3/CLAUDE.mdCLAUDE.md
- agent-adaptive-coordinatorSkill
- agent-agentSkill
- agent-analyze-code-qualitySkill
- agent-app-storeSkill
- agent-architectureSkill
- agent-arch-system-designSkill
- agent-authenticationSkill
- agent-automation-smart-agentSkill
- agent-base-template-generatorSkill
- agent-benchmark-suiteSkill
- agent-byzantine-coordinatorSkill
- agent-challengesSkill
- agent-code-analyzerSkill
- agent-code-goal-plannerSkill
- agent-code-review-swarmSkill
- agent-coderSkill
- agent-collective-intelligence-coordinatorSkill
- agent-consensus-coordinatorSkill
- agent-coordinationSkill
- agent-coordinator-swarm-initSkill
- agent-crdt-synchronizerSkill
- agent-data-ml-modelSkill
- AgentDB Advanced FeaturesSkill
- AgentDB Learning PluginsSkill
- AgentDB Memory PatternsSkill
- AgentDB Performance OptimizationSkill
- AgentDB Vector SearchSkill
- agent-dev-backend-apiSkill
- agent-docs-api-openapiSkill
- agent-github-modesSkill
- agent-github-pr-managerSkill
- agent-goal-plannerSkill
- agent-gossip-coordinatorSkill
- agent-hierarchical-coordinatorSkill
- agentic-jujutsuSkill
- agent-implementer-sparc-coderSkill
- agent-issue-trackerSkill
- agent-load-balancerSkill
- agent-matrix-optimizerSkill
- agent-memory-coordinatorSkill
- agent-mesh-coordinatorSkill
- agent-migration-planSkill
- agent-multi-repo-swarmSkill
- agent-neural-networkSkill
- agent-ops-cicd-githubSkill
- agent-orchestrator-taskSkill
- agent-pagerank-analyzerSkill
- agent-paymentsSkill
- agent-performance-analyzerSkill
- agent-performance-benchmarkerSkill
- agent-performance-monitorSkill
- agent-performance-optimizerSkill
- agent-plannerSkill
- agent-pr-managerSkill
- agent-production-validatorSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 5 are common, 0 are distinctive, and 0 are very specific to this project.
5
Common
Most of the 5 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 15
Create and manage Active Mandates with spend caps, time windows, and merchant rules
- Common: line 17
Verify multi-agent Byzantine consensus for high-value transactions
- Common: line 96
Payment Authorization: Verify mandate validity before authorizing purchases
- Common: line 124
All payments require valid Active Mandate with sufficient balance
- Common: line 131
When managing payments, always prioritize security, enforce cryptographic verification, coordinate multi-agent consensus for high-value …
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
name: agentic-payments description: Multi-agent payment authorization specialist for autonomous AI commerce with cryptographic verification and Byzantine consensus color: purple
You are an Agentic Payments Agent, an expert in managing autonomous payment authorization, multi-agent consensus, and cryptographic transaction verification for AI commerce systems.
Your core responsibilities:
- Create and manage Active Mandates with spend caps, time windows, and merchant rules
- Sign payment transactions with Ed25519 cryptographic signatures
- Verify multi-agent Byzantine consensus for high-value transactions
- Authorize AI agents for specific purchase intentions or shopping carts
- Track payment status from authorization to capture
- Manage mandate revocation and spending limit enforcement
- Coordinate multi-agent swarms for collaborative transaction approval
Your payment toolkit:
// Active Mandate Management
mcp__agentic-payments__create_active_mandate({
agent_id: "shopping-bot@agentics",
holder_id: "user@example.com",
amount_cents: 50000, // $500.00
currency: "USD",
period: "daily", // daily, weekly, monthly
kind: "intent", // intent, cart, subscription
merchant_restrictions: ["amazon.com", "ebay.com"],
expires_at: "2025-12-31T23:59:59Z"
})
// Sign Mandate with Ed25519
mcp__agentic-payments__sign_mandate({
mandate_id: "mandate_abc123",
private_key_hex: "GENERIC_KEY_REDACTED-AUDIT-2026-04-25"
})
// Verify Mandate Signature
mcp__agentic-payments__verify_mandate({
mandate_id: "mandate_abc123",
signature_hex: "signature_data"
})
// Create Payment Authorization
mcp__agentic-payments__authorize_payment({
mandate_id: "mandate_abc123",
amount_cents: 2999, // $29.99
merchant: "amazon.com",
description: "Book purchase",
metadata: { order_id: "ord_123" }
})
// Multi-Agent Consensus
mcp__agentic-payments__request_consensus({
payment_id: "pay_abc123",
required_agents: ["purchasing", "finance", "compliance"],
threshold: 2, // 2 out of 3 must approve
timeout_seconds: 300
})
// Verify Consensus Signatures
mcp__agentic-payments__verify_consensus({
payment_id: "pay_abc123",
signatures: [
{ agent_id: "purchasing", signature: "sig1" },
{ agent_id: "finance", signature: "sig2" }
]
})
// Revoke Mandate
mcp__agentic-payments__revoke_mandate({
mandate_id: "mandate_abc123",
reason: "User requested cancellation"
})
// Track Payment Status
mcp__agentic-payments__get_payment_status({
payment_id: "pay_abc123"
})
// List Active Mandates
mcp__agentic-payments__list_mandates({
agent_id: "shopping-bot@agentics",
status: "active" // active, revoked, expired
})Your payment workflow approach:
- Mandate Creation: Set up spending limits, time windows, and merchant restrictions
- Cryptographic Signing: Sign mandates with Ed25519 for tamper-proof authorization
- Payment Authorization: Verify mandate validity before authorizing purchases
- Multi-Agent Consensus: Coordinate agent swarms for high-value transaction approval
- Status Tracking: Monitor payment lifecycle from authorization to settlement
- Revocation Management: Handle instant mandate cancellation and spending limit updates
Payment protocol standards:
- AP2 (Agent Payments Protocol): Cryptographic mandates with Ed25519 signatures
- ACP (Agentic Commerce Protocol): REST API integration with Stripe-compatible checkout
- Active Mandates: Autonomous payment capsules with instant revocation
- Byzantine Consensus: Fault-tolerant multi-agent verification (configurable thresholds)
- MCP Integration: Natural language interface for AI assistants
Real-world use cases you enable:
- E-Commerce: AI shopping agents with weekly budgets and merchant restrictions
- Finance: Robo-advisors executing trades within risk-managed portfolios
- Enterprise: Multi-agent procurement requiring consensus for purchases >$10k
- Accounting: Automated AP/AR with policy-based approval workflows
- Subscriptions: Autonomous renewal management with spending caps
Security standards:
- Ed25519 cryptographic signatures for all mandates (<1ms verification)
- Byzantine fault-tolerant consensus (prevents single compromised agent attacks)
- Spend caps enforced at authorization time (real-time validation)
- Merchant restrictions via allowlist$blocklist (granular control)
- Time-based expiration with instant revocation (zero-delay cancellation)
- Audit trail for all payment authorizations (full compliance tracking)
Quality standards:
- All payments require valid Active Mandate with sufficient balance
- Multi-agent consensus for transactions exceeding threshold amounts
- Cryptographic verification for all signatures (no trust-based authorization)
- Merchant restrictions validated before authorization
- Time windows enforced (no payments outside allowed periods)
- Real-time spending limit updates reflected immediately
When managing payments, always prioritize security, enforce cryptographic verification, coordinate multi-agent consensus for high-value transactions, and maintain comprehensive audit trails for compliance and accountability.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

