[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EA9D7Q1WDXVR4QGDZ8Z76M":3,"skill-same:01M7EA9D7Q1WDXVR4QGDZ8Z76M":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M7EA9D7Q1WDXVR4QGDZ8Z76M","mpp-agent",null,"Pay HTTP 402 APIs via Machine Payments Protocol (MPP).","sanjeevafk\u002Fagent-skills","sanjeevafk","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F230678117?v=4","01M7C540EFY46ETG1NNWKS5X3Q","Sanjeev","01M7C540F366J5C1D587BMKH9Q",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fhermes-agent\u002Fskills\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":24,"license":15,"version":25,"metadata":26,"platforms":37,"description":7},"Teknium (teknium1), Hermes Agent","0.1.0",{"hermes":27},{"tags":28,"related_skills":34},[29,30,31,32,33],"Payments","MPP","HTTP-402","Tempo","Stripe",[35,36],"stripe-link-cli","stripe-projects",[38,39],"linux","macos","main","4e084e84eb42fc53e144c89c0f7f48b39c8a4b0f","collections\u002Fhermes-agent\u002Fskills\u002Fmpp-agent",1,"https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills","https:\u002F\u002Fgithub.com\u002Fsanjeevafk","First make it work. Then make it right. Then make it fast.","2026-11-14 13:36:16",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add sanjeevafk\u002Fagent-skills --skill mpp-agent",{"tool":54,"command":55},"bunx","bunx skills add sanjeevafk\u002Fagent-skills --skill mpp-agent",{"tool":57,"command":58},"pnpm","pnpm dlx skills add sanjeevafk\u002Fagent-skills --skill mpp-agent","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fcollections\u002Fhermes-agent\u002Fskills\u002Fmpp-agent\u002FSKILL.md",true,[],[63,70,78,87,95,102],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EFHX67M3KKXT1BXVPA5ADT","zarr-python","Chunked N-D arrays for cloud storage (Zarr-Python 3). Compressed arrays, parallel I\u002FO, S3\u002FGCS via fsspec, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":74,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7EFFQGM51TZBGRENXY50ZYM","whiteboard-diagrams","Create accurate, simple, hand-drawn whiteboard diagrams from a user's process, system, architecture, learning workflow, comparison, or causal explanation. Use when the user asks for a scribbly whiteboard visual, educational workflow graphic, hand-drawn explainer, or diagram like the bundled reference; ask one focused clarification question when the subject or relationships are missing, then generate and visually verify the final image.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwhiteboard-diagrams\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwhiteboard-diagrams\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7EFF1CSQNTDMHFK4ZGY6NYK","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7EFE8106X6C28FT8PA74427","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7EFCSNZM9G7ZHS6F127Q71X","verification-loop","A comprehensive verification system for Claude Code sessions.","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M7EFCE7EZMKPRYDDNKBQ9EEH","vercel-deploy","Deploy applications and websites to Vercel. Use when the user requests deployment actions like \"deploy my app\", \"deploy and give me the link\", \"push this live\", or \"create a preview deployment\".","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-deploy\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsanjeevafk\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-deploy\u002FSKILL.md",[],[]]