Agent skill

Moneyclaw

by Matchameleon in Matchameleon/moneyclaw

Inspect a MoneyClaw wallet, create bounded payment tasks, and continue user-confirmed payment steps using a prepaid account.

MITAuto-check passed

Install Moneyclaw

skills CLI

$ npx skills add Matchameleon/moneyclaw --skill moneyclaw -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Matchameleon/moneyclaw moneyclaw --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Matchameleon/moneyclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/moneyclaw-skill .claude/skills/moneyclaw && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "moneyclaw" agent skill from https://github.com/Matchameleon/moneyclaw/tree/main/moneyclaw-skill into .claude/skills/moneyclaw/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "moneyclaw", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Matchameleon/moneyclaw/tree/main/moneyclaw-skill

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Matchameleon/moneyclaw --skill moneyclaw -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Matchameleon/moneyclaw moneyclaw --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Matchameleon/moneyclaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/moneyclaw-skill .agents/skills/moneyclaw && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "moneyclaw" agent skill from https://github.com/Matchameleon/moneyclaw/tree/main/moneyclaw-skill into .agents/skills/moneyclaw/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "moneyclaw", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Matchameleon/moneyclaw --skill moneyclaw -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Matchameleon/moneyclaw moneyclaw --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Matchameleon/moneyclaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/moneyclaw-skill .cursor/skills/moneyclaw && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "moneyclaw" agent skill from https://github.com/Matchameleon/moneyclaw/tree/main/moneyclaw-skill into .cursor/skills/moneyclaw/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "moneyclaw", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Matchameleon/moneyclaw.git --path moneyclaw-skill

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Matchameleon/moneyclaw --skill moneyclaw -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Matchameleon/moneyclaw moneyclaw --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Matchameleon/moneyclaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/moneyclaw-skill .gemini/skills/moneyclaw && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "moneyclaw" agent skill from https://github.com/Matchameleon/moneyclaw/tree/main/moneyclaw-skill into .gemini/skills/moneyclaw/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "moneyclaw", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Matchameleon/moneyclaw moneyclaw

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Matchameleon/moneyclaw --skill moneyclaw -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Matchameleon/moneyclaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/moneyclaw-skill .github/skills/moneyclaw && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "moneyclaw" agent skill from https://github.com/Matchameleon/moneyclaw/tree/main/moneyclaw-skill into .github/skills/moneyclaw/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "moneyclaw", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Matchameleon/moneyclaw --skill moneyclaw -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Matchameleon/moneyclaw moneyclaw --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Matchameleon/moneyclaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/moneyclaw-skill .opencode/skills/moneyclaw && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "moneyclaw" agent skill from https://github.com/Matchameleon/moneyclaw/tree/main/moneyclaw-skill into .opencode/skills/moneyclaw/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "moneyclaw", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: moneyclaw
GitHub stars: 138
Token cost: ~2k tokens
SKILL.md length: 957 words
Files: 5 (incl. references)
Skills in repo: 1
Repo updated: Sep 14, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Inspect a MoneyClaw wallet, create bounded payment tasks, and continue user-confirmed payment steps using a prepaid account.

Works in 5 steps: Check account readiness → Create an auditable payment task → Inspect the payment task state → …
Clearly asks to use MoneyClaw for their own payments
SKILL.md covers Authentication, Trust Model, Approval Model and Safety Boundaries, plus 6 more sections
Calls curl; reaches moneyclaw.ai; needs MONEYCLAW_API_KEY

What it does

Moneyclaw is an agent skill from Matchameleon/moneyclaw. Inspect a MoneyClaw wallet, create bounded payment tasks, and continue user-confirmed payment steps using a prepaid account. Use only when the user clearly asks to use MoneyClaw for their own payments.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `README.md`, `agents/openai.yaml` and `references/acquiring.md`).

The repository describes itself as: openclaw agents for prepaid wallet, virtual card, OTP inbox, public docs, and skill. The licence is MIT.

When your agent uses it

Clearly asks to use MoneyClaw for their own payments

Example prompts

“/moneyclaw”

Requirements

A credential in MONEYCLAW_API_KEY

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Check account readiness
Create an auditable payment task
Inspect the payment task state
Read the payment task history
Continue the approved payment step

What it can do on your machine

Read from SKILL.md and the folder at commit f056ced. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- curl
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- moneyclaw.ai
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- MONEYCLAW_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Moneyclaw loads about 2k tokens when it runs, and up to ~3.6k if it reads all its reference files. Until then it costs about 53 tokens; SKILL.md has 957 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~53
When it runs · the whole SKILL.md, loaded when a task matches: ~2k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~3.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Matchameleon/moneyclaw at commit f056ced, republished under its MIT licence (© Matchameleon). 957 words, ~2,006 tokens.

Download SKILL.mdSave it as .claude/skills/moneyclaw/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.

name: moneyclaw
description: Inspect a MoneyClaw wallet, create bounded payment tasks, and continue user-confirmed payment steps using a prepaid account. Use only when the user clearly asks to use MoneyClaw for their own payments.

MoneyClaw

MoneyClaw helps OpenClaw agents inspect prepaid payment state, create auditable payment tasks, and continue explicitly requested payment steps.

Primary use case: buyer-side payments for OpenClaw agents.

Authentication

This skill requires one MoneyClaw API key.

bash

Authorization: Bearer $MONEYCLAW_API_KEY

Base URL: https://moneyclaw.ai/api

Trust Model

MoneyClaw is designed for real, user-authorized agent payments.

use prepaid balances to keep risk bounded
use payment intents as the main auditable execution surface
keep account inbox state inspectable for receipts and account messages
let the user approve the payment step before money moves

Approval Model

Default to dashboard approval unless the account has explicitly enabled agent auto-approval.

MoneyClaw accounts expose an account-level agentAutoApproveEnabled flag through GET /api/me.
When that flag is off, API-key-created payment tasks wait for dashboard approval before spending.
When that flag is on, API-key-created payment tasks can be auto-approved within the merchant and amount scope of the task.
Do not assume agent auto-approval is enabled unless the account state confirms it.

Safety Boundaries

Only use MoneyClaw for purchases or payment flows explicitly requested by the user. If the account is not clearly configured for agent auto-approval and the user has not explicitly asked for the next payment step, stop and ask.
Only use wallet, card, and billing data returned by the user's own MoneyClaw account.
Respect merchant, issuer, card-network, and verification controls.
Treat fraud checks, KYC, sanctions, geography rules, merchant restrictions, issuer declines, and other payment controls as hard boundaries.
Never fabricate billing identity, cardholder data, addresses, names, phone numbers, or verification information.
If a transaction fails, looks suspicious, or produces conflicting signals, stop and inspect transaction state before retrying.
Prefer prepaid, bounded-risk flows by default.
Never invoke this skill automatically from a shopping, billing, or checkout page. Use it only after an explicit user request to use MoneyClaw.

Before Any High-Risk Step

Before any action that can spend funds, retrieve execution details, or submit a payment step:

Confirm the exact merchant domain.
Confirm the amount and currency.
Confirm the user explicitly asked for this exact action, or that the account is clearly configured for agent auto-approval for this scope.
Stop if that confirmation is missing or ambiguous.

Default Buyer Flow

Use the product in this order:

GET /api/me for wallet readiness, deposit address, and inbox context. Fresh accounts may also finish mailbox, deposit-address, and provider setup on this first authenticated read.
POST /api/payment-intents for the exact purchase.
If agentAutoApproveEnabled is off, wait for dashboard approval. If it is on, the API-key task can move directly toward approved and card_ready. Approved tasks can auto-prepare or reuse the account's hidden execution card when wallet funding is available. On the first hidden-card bootstrap for an account, MoneyClaw may reserve the provider minimum initial deposit onto that shared hidden card even if the current task amount is smaller. Any residual stays on the same hidden card for later tasks.
Use GET /api/payment-intents/:intentId/credentials only when the task is card_ready and the user explicitly asked to continue the current payment step.
After a successful one-time checkout, use POST /api/payment-intents/:intentId/reconcile to write the settled charge back into MoneyClaw accounting.
Inspect payment-task state and wallet transactions before retrying.

Load References When Needed

Read references/payment-safety.md before entering payment details on an unfamiliar merchant, when a checkout keeps failing, or when retry boundaries matter.

Core Jobs

Show full SKILL.md (406 more words)Show less

1. Check account readiness

bash

curl -H "Authorization: Bearer $MONEYCLAW_API_KEY" \
  https://moneyclaw.ai/api/me

Important fields:

balance: wallet balance
depositAddress: where to send USDT
mailboxAddress: inbox address for receipts and account messages
agentAutoApproveEnabled: whether API-key-created payment tasks can auto-approve without a dashboard click

When the user asks for readiness, report wallet balance, deposit address, inbox state, and whether a payment task can proceed.

2. Create an auditable payment task

bash

curl -X POST -H "Authorization: Bearer $MONEYCLAW_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "intentType": "one_time_purchase",
    "merchantName": "OpenAI",
    "merchantDomain": "openai.com",
    "expectedAmount": "20.00",
    "fundingCap": "20.00",
    "currency": "USD",
    "metadata": {
      "serviceName": "ChatGPT Plus"
    }
  }' \
  https://moneyclaw.ai/api/payment-intents

Use payment intents to hold merchant context, approval state, and audit history.

Rules:

use the account's agentAutoApproveEnabled state as the default control path for API-key-created tasks
if the account does not have agent auto-approval enabled and the intent is pending_approval, stop and ask the user to approve it in the dashboard instead of pretending you can finish approval yourself
treat the intent as the source of truth for execution state, not the card

3. Inspect the payment task state

bash

curl -H "Authorization: Bearer $MONEYCLAW_API_KEY" \
  https://moneyclaw.ai/api/payment-intents/{intentId}

Use the payment task as the source of truth for readiness, approval, execution, and completion.

4. Read the payment task history

bash

curl -H "Authorization: Bearer $MONEYCLAW_API_KEY" \
  https://moneyclaw.ai/api/payment-intents/{intentId}/history

Use the history when the user wants an audit trail or when a payment step gave ambiguous results.

5. Continue the approved payment step

bash

curl -H "Authorization: Bearer $MONEYCLAW_API_KEY" \
  https://moneyclaw.ai/api/payment-intents/{intentId}/credentials

Rules:

only call this when the intent is card_ready
only call this after the user explicitly asked to continue that payment step
do not treat these execution details as a general account-level card surface
do not expose PAN or CVV longer than needed for the active checkout

Payment Execution Rules

The spending model is prepaid. The loaded balance is the hard limit.
Fresh accounts may need enough wallet balance for the first shared hidden-card bootstrap, not only for the immediate merchant total.
Before payment, confirm the merchant domain and total amount are correct.
Use the billing address returned by MoneyClaw. Never invent one.
If a merchant asks for unexpected out-of-band verification, stop and ask the user instead of assuming the skill should continue automatically.
Do not retry the same merchant checkout more than twice in one session without user confirmation or clear pre-authorization.
If the user asks for a risky or suspicious payment, stop and explain why.

Use references/payment-safety.md for expanded safety and retry guidance.

Good Default Prompt Shapes

Check my MoneyClaw account and tell me if the wallet, inbox, and payment tasks are ready.
Create a payment task for this purchase and keep the amount bounded to the expected total.
Continue this already approved payment step.
Check whether this payment task completed, still needs dashboard approval, or should be inspected before retrying.

Files

SKILL.md and 4 other files (references) in moneyclaw-skill of Matchameleon/moneyclaw.

SKILL.md
README.md
agents/openai.yaml
references/acquiring.md
references/payment-safety.md

Open the folder on GitHubat commit f056ced

Compare with similar skills

Moneyclaw next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Moneyclaw compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Moneyclaw this skillMatchameleon/moneyclaw	138	—	~2k	Automated safety check: Pass	MIT	27 days ago
Analyzing Ransomware Payment Walletsmukul975/Anthropic-Cybersecurity-Skills	34k	—	~1.9k	Automated safety check: Pass	Apache-2.0	1 mo ago
Wallet PaymentsBitterbot-AI/bitterbot-desktop	2.5k	—	~1.1k	Automated safety check: Pass	MIT	today
Continuetelegramdesktop/tdesktop	33k	2 repos	~9.4k	Automated safety check: Pass	GPL-3.0	today
Agent Payment X402affaan-m/ECC	276k	—	~6.8k	Automated safety check: Pass	MIT	yesterday
Node Inspect Debuggeropenclaw/openclaw	392k	1 repos	~894	Automated safety check: Pass	MIT	today

Similar skills

Analyzing Ransomware Payment Wallets
mukul975/Anthropic-Cybersecurity-Skills
Traces ransomware cryptocurrency payment flows using blockchain analysis tools such as Chainalysis Reactor, WalletExplorer, and blockchain.com APIs, identifying wallet clusters and tracking fund…
34k GitHub stars~1.9k tokensUpdated 1 mo ago
SecurityAuto-check passed
Wallet Payments
Bitterbot-AI/bitterbot-desktop
A skill your agent uses when webfetch returns HTTP 402, an API offers a paid tier or micro-toll, another agent charges USDC, or the user asks you to pay, tip or buy.
2.5k GitHub stars~1.1k tokensUpdated today
Auto-check passed
Continue
telegramdesktop/tdesktop
Continue autonomous Telegram Desktop development from the shared ai-tdesktop repository.
33k GitHub starsUsed in 2 repos~9.4k tokens
Productivity & AutomationAuto-check passed
Agent Payment X402
affaan-m/ECC
Add x402 payment execution to AI agents with per-task budgets, spending controls, and non-custodial wallets.
276k GitHub stars~6.8k tokensUpdated yesterday
Backend & APIsAuto-check passed
Node Inspect Debugger
openclaw/openclaw
Debug Node.js with node inspect, --inspect, breakpoints, CDP, heap, and CPU profiles.
392k GitHub starsUsed in 1 repo~894 tokens
Frontend & DesignAuto-check passed
Continuous Learning
affaan-m/ECC
[DEPRECATED - use continuous-learning-v2] Legacy v1 stop-hook skill extractor.
276k GitHub stars~1.1k tokensUpdated yesterday
Auto-check passed

Questions about Moneyclaw

What does Moneyclaw do?

Inspect a MoneyClaw wallet, create bounded payment tasks, and continue user-confirmed payment steps using a prepaid account. Moneyclaw is an agent skill from Matchameleon/moneyclaw. Inspect a MoneyClaw wallet, create bounded payment tasks, and continue user-confirmed payment steps using a prepaid account.

When should I use Moneyclaw?

Moneyclaw fits situations like: clearly asks to use MoneyClaw for their own payments.

How do I install Moneyclaw in Claude Code?

Run `npx skills add Matchameleon/moneyclaw --skill moneyclaw -a claude-code`. Or copy the skill folder (moneyclaw-skill in Matchameleon/moneyclaw) into .claude/skills/moneyclaw in your project. Claude Code loads it when a task matches its description.

How do I install Moneyclaw in Codex?

Run `npx skills add Matchameleon/moneyclaw --skill moneyclaw -a codex`. Or copy the skill folder (moneyclaw-skill in Matchameleon/moneyclaw) into .agents/skills/moneyclaw in your project. Codex loads it when a task matches its description.

Can I use Moneyclaw in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Matchameleon/moneyclaw --skill moneyclaw -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/moneyclaw, .gemini/skills/moneyclaw, .github/skills/moneyclaw and .opencode/skills/moneyclaw in your project.

What does Moneyclaw need to run?

Going by SKILL.md and its folder, Moneyclaw needs the command-line tools its instructions call (curl) and credentials named MONEYCLAW_API_KEY. Our summary lists: A credential in MONEYCLAW_API_KEY.

Does Moneyclaw access the network?

SKILL.md names 1 domain. In commands or code: moneyclaw.ai; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Moneyclaw safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Moneyclaw use?

Moneyclaw is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Moneyclaw use?

About 2k tokens (SKILL.md is roughly 8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.6k tokens, read only when the agent opens those files.

What are the alternatives to Moneyclaw?

Skills that share tags, products or a category with Moneyclaw: Analyzing Ransomware Payment Wallets (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Wallet Payments (Bitterbot-AI/bitterbot-desktop, 2.5k stars), Continue (telegramdesktop/tdesktop, 33k stars) and Agent Payment X402 (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Moneyclaw?

Matchameleon (a GitHub user) maintains it in Matchameleon/moneyclaw, which has 138 GitHub stars. The repository was last updated on September 14, 2026.

Source: Matchameleon/moneyclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Moneyclaw

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

MoneyClaw

Authentication

Trust Model

Approval Model

Safety Boundaries

Before Any High-Risk Step

Default Buyer Flow

Load References When Needed

Core Jobs

1. Check account readiness

2. Create an auditable payment task

3. Inspect the payment task state

4. Read the payment task history

5. Continue the approved payment step

Payment Execution Rules

Good Default Prompt Shapes

Files

Compare with similar skills

Similar skills

Analyzing Ransomware Payment Wallets

Wallet Payments

Continue

Agent Payment X402

Node Inspect Debugger

Continuous Learning

Questions about Moneyclaw