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.
/plugin marketplace add paid-tw/skillsnpx agentmods add plugins/paid-tw/skills/newebpaygit clone --depth 1 https://github.com/paid-tw/skillsWrote 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/plugins/paid-tw/skills/newebpay)<a href="https://agentmods.dev/plugins/paid-tw/skills/newebpay"><img src="https://agentmods.dev/badge/plugins/paid-tw/skills/newebpay.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
newebpay 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- payuni — 86% identical, 10 lines differ
What it actually says
{
"name": "newebpay",
"version": "2.2.0",
"description": "藍新金流(NewebPay)完整串接工具 - 支付串接、交易查詢、退款",
"author": {
"name": "paid-tw",
"email": "[email protected]",
"url": "https://github.com/paid-tw"
},
"homepage": "https://github.com/paid-tw/skills#newebpay",
"repository": "https://github.com/paid-tw/skills",
"license": "MIT",
"keywords": ["taiwan", "payment", "newebpay", "藍新", "金流", "credit-card", "line-pay", "atm", "cvs"],
"hooks": "./hooks/hooks.json"
}
What it installs
The manifest is a name and a version. 4 skills, 1 agent travel with it, and installing the plugin installs all of them — 195 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 4d ago First seen · 16 lines scan A c259ebf385ed
newebpay is a plugin published in the GitHub repository paid-tw/skills (276 stars, last pushed 6mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-30.
Other plugins, from other repositories
jpm-payments-skills
Conversational agent skills that walk a merchant from J.P. Morgan Payments onboarding through a working API integration. Supports Checkout and Online Payments in the initial release. Generates language-specific OAuth modules (Node/TypeScript, Python, Java idiomatic; other languages via canonical algorithm).
sumup-skills
Skills for SumUp payment integrations across terminal and online checkout flows.
shipshitdev-payments
Payment processing and financial integrations.
stripe-implementer
Implement Stripe payment processing, subscription management, webhook handling, and customer management in Next.js and NestJS applications. Use when integrating Stripe payments, subscription billing, webhooks, customer management, or checkout and payment intents.
dodo-best-practices
Guide for initial Dodo Payments setup, including SDK installation, test and live environments, API keys, and the canonical checkout-to-webhook architecture.
checkout-integration
Guide for starting hosted Checkout Sessions, payment links, and overlay or inline checkout for one-time and recurring products; use subscription-integration for post-checkout lifecycle management.