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 perniemann/pnCore --skill pn-payment-integrationgit clone --depth 1 https://github.com/perniemann/pnCoreWrote 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/perniemann/pncore/pn-payment-integration)<a href="https://agentmods.dev/skills/perniemann/pncore/pn-payment-integration"><img src="https://agentmods.dev/badge/skills/perniemann/pncore/pn-payment-integration/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/perniemann/pncore/pn-payment-integration"><img src="https://agentmods.dev/badge/skills/perniemann/pncore/pn-payment-integration.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.00034 | $0.00453 |
| Opus 5 | $0.00017 | $0.00227 |
| Sonnet 5 | $0.00007 | $0.00091 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
pn-payment-integration 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 6d 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.
What it actually says
Payment integration
When to use
- Implementing payments, billing, or subscription features
- Checkout flows and payment forms
- Webhook handling for payment events
- Migrating from test to production payment mode
When Stripe MCP is available: Use its tools for Stripe API lookups, product/price/subscription schema, SDK examples, and Stripe-specific operations. Combine with this skill for checkout patterns, webhooks, idempotency, and PCI guidance. Do not duplicate Stripe docs manually when MCP can provide them.
Focus areas
- Stripe / PayPal / Square API integration
- Checkout flows and payment forms
- Subscription billing and recurring payments
- Webhook handling for payment events
- PCI compliance and security best practices
- Payment error handling and retry logic
Approach
- Security first — Never log sensitive card data; use official SDKs.
- Idempotency — Implement for all payment operations (create intent, confirm, refund).
- Edge cases — Handle failed payments, disputes, refunds, webhook retries.
- Test mode first — Clear migration path to production; separate API keys per environment.
- Webhooks — Comprehensive handling for async events; verify signatures; handle duplicate delivery.
Output
- Payment integration code with error handling
- Webhook endpoint implementations (verify signature, idempotent handlers)
- Database schema for payment records (status, idempotency keys)
- Security checklist (PCI compliance points)
- Test payment scenarios and edge cases
- Environment variable configuration (API keys, webhook secrets)
Sources
- PCI SSC Data Security Standard (PCI DSS) v4.0 — https://www.pcisecuritystandards.org/
- Reference pn-security-audit for auth and API security
Guardrails
- Always use official SDKs; include both server-side and client-side code where needed
- Reference pn-security-audit for auth and API security
- Reference pn-node-api for env/secrets and error handling
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.
- 6d ago First seen · 53 lines · 34 tokens per session scan A c55dcbc9b9ae
pn-payment-integration is a skill published in the GitHub repository perniemann/pnCore (0 stars, last pushed 3d ago), licensed MIT. It adds 34 tokens to every session and 453 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-09-03.
Other skills, from other repositories
stripe-best-practices
Guides Stripe integration decisions across API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, tax and registrations (Stripe Tax, automatictax, product tax codes), Treasury financial accounts, integration options (Checkout, Payment…
stripe-link-cli
Agent payments via Stripe Link — cards, SPT, approvals.
defi-protocol-templates
Implement DeFi protocols with production-ready templates for staking, AMMs, governance, and flash loans. Use when building decentralized finance applications or smart contract protocols.
typescript
TypeScript coding conventions, best practices, and patterns for writing clean, maintainable code.
comparable-company-analysis
A workflow for comparing a publicly listed company with similar listed companies. It examines their businesses, financial results, competitors, and recent developments.
Braintree Automation
Braintree Automation: manage payment processing via Stripe-compatible tools for customers, subscriptions, payment methods, and transactions.