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.
npx skills add 100xPercent/pop-pay --skill pop-pay-skillgit clone --depth 1 https://github.com/100xPercent/pop-payWrote 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.
[](https://agentmods.dev/skills/100xpercent/pop-pay/pop-pay-skill)<a href="https://agentmods.dev/skills/100xpercent/pop-pay/pop-pay-skill"><img src="https://agentmods.dev/badge/skills/100xpercent/pop-pay/pop-pay-skill/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.
<a href="https://agentmods.dev/skills/100xpercent/pop-pay/pop-pay-skill"><img src="https://agentmods.dev/badge/skills/100xpercent/pop-pay/pop-pay-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00041 | $0.01809 |
| Opus 5 | $0.00020 | $0.00905 |
| Sonnet 5 | $0.00008 | $0.00362 |
| Haiku 4.5 | $0.00004 | $0.00181 |
Grade A, and why
pop-pay 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What This Skill Does
Gives your OpenClaw agent the ability to pay at any online store using your own existing credit card. The card number is stored in a local encrypted vault (AES-256-GCM) and is never placed in the agent's context window. When a payment is approved, credentials are injected directly into the checkout form via Chrome DevTools Protocol (CDP) in a separate local process — if the agent is compromised by prompt injection, the attacker cannot steal the card it never saw.
Tagline: it only takes 0.1% of hallucination to drain 100% of your wallet.
Privacy & Data Flow
All payment logic runs on your machine. There are no Point One Percent / A Hundred Percent Inc. servers in the payment path.
| Component | Default | Data stays |
|---|---|---|
| Card credentials | Local encrypted vault (~/.config/pop-pay/vault.enc) |
Your machine only |
| Spend policy | ~/.config/pop-pay/.env |
Your machine only |
| Guardrail engine | keyword mode (zero API calls) |
Your machine only |
| Guardrail engine (optional) | llm mode — uses your own API key |
Your chosen provider |
Setup (One Time)
Install from npm (https://www.npmjs.com/package/pop-pay):
# No install needed — run on demand via npx
npx -y pop-pay pop-init-vault
Or install globally:
npm install -g pop-pay
pop-init-vault
For stronger protection (recommended — blocks any agent with shell access):
npx -y pop-pay pop-init-vault --passphrase # one-time setup
npx -y pop-pay pop-unlock # run once before each session
Add to your OpenClaw MCP config (or ~/.openclaw/mcp_servers.json):
{
"mcpServers": {
"pop-pay": {
"command": "npx",
"args": ["-y", "pop-pay", "launch-mcp"],
"env": {
"POP_CDP_URL": "http://localhost:9222"
}
}
}
}
Or via the OpenClaw CLI:
openclaw mcp add pop-pay -- npx -y pop-pay launch-mcp
Then launch Chrome with CDP:
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 230 lines · 41 tokens per session scan A 2f0aeaeb59ee
pop-pay is a skill published in the GitHub repository 100xPercent/pop-pay (1 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 1,809 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
pop-pay
Your card stays on your PC — no SaaS, no login, no external account. Credentials inject directly, keeping them out of the AI's context window.
appdirect
Every documented AppDirect marketplace operation in one binary, plus offline sync and billing-reconciliation joins. Trigger phrases: reconcile appdirect billing, which appdirect payments failed this week, what changed in appdirect subscriptions, show my appdirect pipeline, appdirect company 360, use appdirect, run…
favcrm-billing-commerce
Use for invoices, payments, products, orders, promotions, subscriptions, overdue follow-up, and commerce operations in FavCRM.
shop
Use when the user wants Axon-backed product research, product comparisons, review synthesis, budget-aware recommendations, or cart preparation without checkout.
oen-payment
An integration guide for Oen Payment, a payment service supporting credit cards, LINE Pay, and convenience-store payments through a REST API and MCP server.
payment-processing
P-Link is a payment infrastructure designed for humans, APIs, and AI agents. You can use P-Link when you need a payment page (in order to collect payments without any prerequisities, no account, no subscription) or when you want to send payments massively, or programatically.