[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78ZPKKSQMVEMG8ZVMYRPA0Q":3,"skill-same:01M78ZPKKSQMVEMG8ZVMYRPA0Q":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":44,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M78ZPKKSQMVEMG8ZVMYRPA0Q","mpp-agent",null,"Pay HTTP 402 APIs via Machine Payments Protocol (MPP).","ZDStudios\u002FAIOS","ZDStudios","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121779558?v=4","01M788P61KMHSJ87R41BH4MSQM","01M788P627Y27KK5MQ1KG3TW5H",7,"MIT","https:\u002F\u002Fgithub.com\u002FZDStudios\u002FAIOS\u002Fblob\u002Fmain\u002Fhermes-agent-main\u002Fhermes-agent-main\u002Foptional-skills\u002Fpayments\u002Fmpp-agent\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: mpp-agent\ndescription: Pay HTTP 402 APIs via Machine Payments Protocol (MPP).\nversion: 0.1.0\nauthor: Teknium (teknium1), Hermes Agent\nlicense: MIT\nplatforms: [linux, macos]\nmetadata:\n  hermes:\n    tags: [Payments, MPP, HTTP-402, Tempo, Stripe]\n    related_skills: [stripe-link-cli, stripe-projects]\n---\n\n# MPP Agent Skill\n\nWraps the Machine Payments Protocol (MPP, https:\u002F\u002Fmpp.dev) clients so Hermes can pay for per-request API access against servers that respond with `HTTP 402 Payment Required`.\n\nThree client options, all distributed via npm. Pick the lightest one that solves the user's need. Gated `[linux, macos]` while the broader payments tooling matures on Windows.\n\n## When to Use\n\n- A merchant API returns `HTTP 402` with a `www-authenticate` header — and the user wants to actually pay it, not just log the response.\n- The user asks to \"pay per request\", \"set up an agent wallet\", \"use Tempo \u002F Privy \u002F AgentCash\", or wants to discover MPP-priced services.\n- A Stripe Link spend has produced a Shared Payment Token (SPT) and the agent needs to attach it to the 402 challenge — in that flow, prefer `link-cli mpp pay` (see the `stripe-link-cli` skill).\n\n## Choosing a client\n\n| Tool | When | Setup |\n|---|---|---|\n| `link-cli` | User already has Stripe Link set up, or the 402 challenge advertises `method=\"stripe\"` | see the `stripe-link-cli` skill |\n| Tempo Wallet | MPP services with spend controls, service discovery | `tempo wallet login` |\n| Privy Agent CLI | Multi-chain wallets, browser-based funding | `privy-agent-wallets login` |\n| AgentCash | 300+ pre-priced APIs via one USDC.e balance | `npx agentcash onboard` |\n| `mppx` | Dev + debugging, smallest dep surface | `npm install -g mppx` then `mppx account create` |\n\nDefault: if the user already has Stripe Link configured or the 402 challenge specifies `method=\"stripe\"`, use `link-cli mpp pay` (the `stripe-link-cli` skill). Otherwise `mppx` for one-off paid calls and debugging, and Tempo Wallet when the user wants persistent spend controls.\n\n## Prerequisites\n\n- Node.js 20+ on `PATH`\n- A funded wallet (Tempo \u002F Privy \u002F AgentCash) OR an `mppx` account\n- For Tempo \u002F Privy \u002F AgentCash: follow their respective onboarding skills:\n  - `https:\u002F\u002Ftempo.xyz\u002FSKILL.md`\n  - `https:\u002F\u002Fagents.privy.io\u002Fskill.md`\n  - `https:\u002F\u002Fagentcash.dev\u002Fskill.md`\n\nUse `web_extract` to fetch any of those SKILL.md files if the user picks one.\n\n## Procedure (mppx, fastest path)\n\nRun all commands through the `terminal` tool.\n\n### 1. Install + create an account\n\n```\nnpm install -g mppx\nmppx account create\n```\n\nStore the resulting account credentials wherever the CLI tells you (the CLI writes them under its own config — do not paste them into the agent transcript).\n\n### 2. Inspect the merchant's 402 challenge\n\nIf the user gives you a URL, probe it first to confirm it actually speaks MPP:\n\n```\ncurl -i \u003Curl>\n```\n\nA real MPP 402 looks like:\n\n```\nHTTP\u002F1.1 402 Payment Required\nwww-authenticate: tempo amount=0.1 currency=...\n```\n\n### 3. Pay the request\n\n```\nmppx \u003Curl>\n```\n\nFor non-GET methods or request bodies:\n\n```\nmppx \u003Curl> --method POST --data '\u003Cjson>'\n```\n\n`mppx` handles the 402 challenge\u002Fcredential dance automatically and prints the merchant's actual response on success.\n\n### 4. Verify the receipt\n\n`mppx` attaches the receipt header automatically. To inspect:\n\n```\nmppx \u003Curl> -v\n```\n\n## Procedure (Tempo Wallet)\n\nThe Tempo Wallet skill at https:\u002F\u002Ftempo.xyz\u002FSKILL.md is the canonical reference; fetch it with `web_extract` and follow it. Headline:\n\n```\ntempo wallet login\ntempo wallet pay \u003Curl>\n```\n\nSpend controls and service discovery live in the wallet UI at https:\u002F\u002Fwallet.tempo.xyz.\n\n## Pitfalls\n\n- **`HTTP 402` without `method=\"stripe\"` cannot be paid by Stripe Link.** If the challenge advertises only Tempo \u002F other methods, use `mppx` (or whichever wallet matches) — Link will reject it. Conversely, if it advertises `method=\"stripe\"`, prefer Link via the `stripe-link-cli` skill so the spend goes through the user's approved card.\n- **Multiple challenges in one header.** `www-authenticate` may list several methods (e.g. `tempo, stripe`). The Link CLI's `mpp decode` will pick the Stripe one; `mppx` will pick Tempo. There's no single \"right\" client — pick by which wallet the user has funded.\n- **Zero-amount challenges.** Some MPP endpoints charge `$0.00` and just want a proof credential. These work without a funded wallet. Don't refuse them as \"broken.\"\n- **Wallet keys never enter agent context.** All four clients store keys under their own config dirs (or generate per-session ephemeral keypairs, in Privy's case). Do not `cat`\u002F`read_file` them.\n- **Server-side MPP is a different skill.** If the user wants to ADD 402 to their own API, this skill is wrong — point them at https:\u002F\u002Fmpp.dev\u002Fquickstart\u002Fserver and the `mppx\u002Fnextjs` \u002F `mppx\u002Fhono` \u002F `mppx\u002Fexpress` \u002F `mppx\u002Felysia` middlewares. A dedicated `mpp-server` skill may land later.\n\n## Verification\n\n```\nmppx --version && mppx account list\n```\n\nExit code 0 means installed and an account exists.\n","# MPP Agent Skill\n\nWraps the Machine Payments Protocol (MPP, https:\u002F\u002Fmpp.dev) clients so Hermes can pay for per-request API access against servers that respond with `HTTP 402 Payment Required`.\n\nThree client options, all distributed via npm. Pick the lightest one that solves the user's need. Gated `[linux, macos]` while the broader payments tooling matures on Windows.\n\n## When to Use\n\n- A merchant API returns `HTTP 402` with a `www-authenticate` header — and the user wants to actually pay it, not just log the response.\n- The user asks to \"pay per request\", \"set up an agent wallet\", \"use Tempo \u002F Privy \u002F AgentCash\", or wants to discover MPP-priced services.\n- A Stripe Link spend has produced a Shared Payment Token (SPT) and the agent needs to attach it to the 402 challenge — in that flow, prefer `link-cli mpp pay` (see the `stripe-link-cli` skill).\n\n## Choosing a client\n\n| Tool | When | Setup |\n|---|---|---|\n| `link-cli` | User already has Stripe Link set up, or the 402 challenge advertises `method=\"stripe\"` | see the `stripe-link-cli` skill |\n| Tempo Wallet | MPP services with spend controls, service discovery | `tempo wallet login` |\n| Privy Agent CLI | Multi-chain wallets, browser-based funding | `privy-agent-wallets login` |\n| AgentCash | 300+ pre-priced APIs via one USDC.e balance | `npx agentcash onboard` |\n| `mppx` | Dev + debugging, smallest dep surface | `npm install -g mppx` then `mppx account create` |\n\nDefault: if the user already has Stripe Link configured or the 402 challenge specifies `method=\"stripe\"`, use `link-cli mpp pay` (the `stripe-link-cli` skill). Otherwise `mppx` for one-off paid calls and debugging, and Tempo Wallet when the user wants persistent spend controls.\n\n## Prerequisites\n\n- Node.js 20+ on `PATH`\n- A funded wallet (Tempo \u002F Privy \u002F AgentCash) OR an `mppx` account\n- For Tempo \u002F Privy \u002F AgentCash: follow their respective onboarding skills:\n  - `https:\u002F\u002Ftempo.xyz\u002FSKILL.md`\n  - `https:\u002F\u002Fagents.privy.io\u002Fskill.md`\n  - `https:\u002F\u002Fagentcash.dev\u002Fskill.md`\n\nUse `web_extract` to fetch any of those SKILL.md files if the user picks one.\n\n## Procedure (mppx, fastest path)\n\nRun all commands through the `terminal` tool.\n\n### 1. Install + create an account\n\n```\nnpm install -g mppx\nmppx account create\n```\n\nStore the resulting account credentials wherever the CLI tells you (the CLI writes them under its own config — do not paste them into the agent transcript).\n\n### 2. Inspect the merchant's 402 challenge\n\nIf the user gives you a URL, probe it first to confirm it actually speaks MPP:\n\n```\ncurl -i \u003Curl>\n```\n\nA real MPP 402 looks like:\n\n```\nHTTP\u002F1.1 402 Payment Required\nwww-authenticate: tempo amount=0.1 currency=...\n```\n\n### 3. Pay the request\n\n```\nmppx \u003Curl>\n```\n\nFor non-GET methods or request bodies:\n\n```\nmppx \u003Curl> --method POST --data '\u003Cjson>'\n```\n\n`mppx` handles the 402 challenge\u002Fcredential dance automatically and prints the merchant's actual response on success.\n\n### 4. Verify the receipt\n\n`mppx` attaches the receipt header automatically. To inspect:\n\n```\nmppx \u003Curl> -v\n```\n\n## Procedure (Tempo Wallet)\n\nThe Tempo Wallet skill at https:\u002F\u002Ftempo.xyz\u002FSKILL.md is the canonical reference; fetch it with `web_extract` and follow it. Headline:\n\n```\ntempo wallet login\ntempo wallet pay \u003Curl>\n```\n\nSpend controls and service discovery live in the wallet UI at https:\u002F\u002Fwallet.tempo.xyz.\n\n## Pitfalls\n\n- **`HTTP 402` without `method=\"stripe\"` cannot be paid by Stripe Link.** If the challenge advertises only Tempo \u002F other methods, use `mppx` (or whichever wallet matches) — Link will reject it. Conversely, if it advertises `method=\"stripe\"`, prefer Link via the `stripe-link-cli` skill so the spend goes through the user's approved card.\n- **Multiple challenges in one header.** `www-authenticate` may list several methods (e.g. `tempo, stripe`). The Link CLI's `mpp decode` will pick the Stripe one; `mppx` will pick Tempo. There's no single \"right\" client — pick by which wallet the user has funded.\n- **Zero-amount challenges.** Some MPP endpoints charge `$0.00` and just want a proof credential. These work without a funded wallet. Don't refuse them as \"broken.\"\n- **Wallet keys never enter agent context.** All four clients store keys under their own config dirs (or generate per-session ephemeral keypairs, in Privy's case). Do not `cat`\u002F`read_file` them.\n- **Server-side MPP is a different skill.** If the user wants to ADD 402 to their own API, this skill is wrong — point them at https:\u002F\u002Fmpp.dev\u002Fquickstart\u002Fserver and the `mppx\u002Fnextjs` \u002F `mppx\u002Fhono` \u002F `mppx\u002Fexpress` \u002F `mppx\u002Felysia` middlewares. A dedicated `mpp-server` skill may land later.\n\n## Verification\n\n```\nmppx --version && mppx account list\n```\n\nExit code 0 means installed and an account exists.\n",{"name":5,"author":23,"license":14,"version":24,"metadata":25,"platforms":36,"description":7},"Teknium (teknium1), Hermes Agent","0.1.0",{"hermes":26},{"tags":27,"related_skills":33},[28,29,30,31,32],"Payments","MPP","HTTP-402","Tempo","Stripe",[34,35],"stripe-link-cli","stripe-projects",[37,38],"linux","macos","main","4faa79f92720631ffd00755d9a1018f8c68d3619","hermes-agent-main\u002Fhermes-agent-main\u002Foptional-skills\u002Fpayments\u002Fmpp-agent",1,"https:\u002F\u002Fgithub.com\u002FZDStudios\u002FAIOS","https:\u002F\u002Fzdstudios.github.io\u002FAIOS\u002F","https:\u002F\u002Fgithub.com\u002FZDStudios","zdstudios.network","Hacker, Coder and Machine Learning Engineer \r\n","2026-10-06 21:45:38",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add ZDStudios\u002FAIOS --skill mpp-agent",{"tool":55,"command":56},"bunx","bunx skills add ZDStudios\u002FAIOS --skill mpp-agent",{"tool":58,"command":59},"pnpm","pnpm dlx skills add ZDStudios\u002FAIOS --skill mpp-agent","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FZDStudios\u002FAIOS\u002Fblob\u002Fmain\u002Fhermes-agent-main\u002Fhermes-agent-main\u002Foptional-skills\u002Fpayments\u002Fmpp-agent\u002FSKILL.md",true,[],[64,72,79,85,92,99],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":68,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M7910QACPXVF8QY3ZMK6MD2M","ruflo","Ruflo is a multi-agent orchestration platform for AI coding agents (Claude Code, Cursor, Codex, Copilot, Gemini, Amp, +12 more). Use this skill when the user wants to (1) install\u002Finit ruflo in a project, (2) run multi-agent swarms with hierarchical coordination, (3) use ruflo's 314+ MCP tools for memory, routing, hooks, sub-agents, or workflows, (4) check ruflo status\u002Fversion\u002Fdoctor health, or (5) discover which of ruflo's 30+ plugins fits their task.","https:\u002F\u002Fgithub.com\u002FZDStudios\u002FAIOS\u002Fblob\u002Fmain\u002Fruflo-main\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FZDStudios\u002FAIOS\u002Fblob\u002Fmain\u002Fruflo-main\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M790G7AX480HX5959531CWBK","ponytail","Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says \"ponytail\", \"be lazy\", \"lazy mode\", \"simplest solution\", \"minimal solution\", \"yagni\", \"do less\", or \"shortest path\", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).","https:\u002F\u002Fgithub.com\u002FZDStudios\u002FAIOS\u002Fblob\u002Fmain\u002Fponytail-main\u002Fskills\u002Fponytail\u002FSKILL.md",[],[],{"skillNo":80,"name":74,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M790FD2BC49T1M774T6NND33","Lazy senior dev mode for any coding task (write, refactor, fix, review): YAGNI, stdlib first, no unrequested abstractions. Not for non-coding requests.","https:\u002F\u002Fgithub.com\u002FZDStudios\u002FAIOS\u002Fblob\u002Fmain\u002Fponytail-main\u002F.openclaw\u002Fskills\u002Fponytail\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M790FANKMMJJQK23GQEESEXP","ponytail-review","Review a diff for over-engineering. Finds what to delete: reinvented stdlib, needless deps, speculative abstractions. One line per finding.","https:\u002F\u002Fgithub.com\u002FZDStudios\u002FAIOS\u002Fblob\u002Fmain\u002Fponytail-main\u002F.openclaw\u002Fskills\u002Fponytail-review\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M790F7Q3SJZCR6BYQ97TVFEJ","ponytail-help","Quick reference for ponytail's modes, skills, and commands. One-shot display.","https:\u002F\u002Fgithub.com\u002FZDStudios\u002FAIOS\u002Fblob\u002Fmain\u002Fponytail-main\u002F.openclaw\u002Fskills\u002Fponytail-help\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":18},"01M790F3TX7VZG0J4VVXE9BSNT","ponytail-gain","Show ponytail measured impact as a scoreboard: less code, less cost, more speed, from the benchmark medians. One-shot display.","https:\u002F\u002Fgithub.com\u002FZDStudios\u002FAIOS\u002Fblob\u002Fmain\u002Fponytail-main\u002F.openclaw\u002Fskills\u002Fponytail-gain\u002FSKILL.md",[],[]]