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 agentmods add skills/nevaberry/nevaberry-plugins/apple-pay-knowledge-patchnpx skills add Nevaberry/nevaberry-plugins --skill apple-pay-knowledge-patchgit clone --depth 1 https://github.com/Nevaberry/nevaberry-pluginsWrote 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/nevaberry/nevaberry-plugins/apple-pay-knowledge-patch)<a href="https://agentmods.dev/skills/nevaberry/nevaberry-plugins/apple-pay-knowledge-patch"><img src="https://agentmods.dev/badge/skills/nevaberry/nevaberry-plugins/apple-pay-knowledge-patch.svg" alt="Measured on agentmods" 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 | $0.00009 | $0.01489 |
| Opus 5 | $0.00005 | $0.00745 |
| Sonnet 5 | $0.00002 | $0.00298 |
| Haiku 4.5 | $0.00001 | $0.00149 |
Grade A, and why
apple-pay-knowledge-patch 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.
How it starts
The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apple Pay Knowledge Patch
Use this skill for Apple Pay work involving:
- Apple Pay JS or Payment Request platform availability.
- SDK delivery, sandbox behavior, or a pinned SDK asset.
- Apple Pay button behavior.
- Merchandising and order-tracking components on the web.
- Recurring, automatic-reload, or deferred payment requests.
- Multimerchant token contexts.
- Merchant-validation sheet updates.
- Merchant category codes on payment requests.
Reference index
| Reference | Topics |
|---|---|
| Web platform and SDK | Regional platform boundaries, SDK delivery, button behavior, sandbox behavior, and the pinned 1.3.8 asset |
| Payment requests | Specialized schedules, multimerchant token contexts, merchant validation, and merchant category codes |
| Merchandising and order tracking | Installment merchandising and the Track with Apple Wallet button |
Apply the guidance
- Identify the integration surface.
- For browser and operating-system eligibility, use Web platform and SDK.
- For payment-request modeling, use Payment requests.
- For installment information or order tracking, use Merchandising and order tracking.
- Preserve the regional distinction in web platform checks.
- Outside China and China have different minimum iOS versions.
- macOS availability also differs by region.
- Keep Apple Pay JS and Payment Request requirements separate.
- Their minimum iOS versions differ.
- Their minimum macOS requirements differ outside China.
- Treat sandbox capability results according to the sandbox-specific rule.
paymentCredentialStatusUnknownis not proof that Apple Pay is unavailable.
- Select only the payment-request primitive that matches the stated payment schedule or update.
What ships with it
4 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.
- 4d ago First seen · 196 lines · 9 tokens per session scan A 616cfb67fcf9
apple-pay-knowledge-patch is a skill published in the GitHub repository Nevaberry/nevaberry-plugins (24 stars, last pushed 7d ago), licensed MIT. It adds 9 tokens to every session and 1,489 once invoked, about $0.0000 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-30.
Other skills, from other repositories
git-pr
For every git repo in the current folder, create and merge a PR for feature-branch work, then return to the default branch and pull. With no arguments this runs fully autonomously across ALL sub-repos — commit → push → PR → squash-merge → checkout main → pull. Use whenever the user asks to commit, ship, push…
stripe
Integrate and manage Stripe payment processing — accept payments, manage subscriptions, generate invoices, handle refunds, and configure webhooks. Covers Stripe Checkout, Payment Intents, Subscriptions, Invoicing, and Connect. Context: User wants to set up Stripe user: "integrate Stripe payments into my app" Context…
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
api-telemetry
Catalog of OpenTelemetry instrumentation built into framework @cyanheads/mcp-ts-core — spans, metrics, completion logs, env config, runtime caveats, custom instrumentation patterns, and cardinality rules. Use when enabling OTel export, adding custom spans or metrics in services, debugging missing telemetry, looking up…
maintenance
Investigate, adopt, and verify dependency updates — with special handling for @cyanheads/mcp-ts-core. Captures what changed, understands why, cross-references against the codebase, adopts framework improvements, syncs project skills, and runs final checks. Supports two entry modes: run the full flow end-to-end, or…