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 PaddleHQ/paddle-agent-skills --skill sandbox-testinggit clone --depth 1 https://github.com/PaddleHQ/paddle-agent-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/skills/paddlehq/paddle-agent-skills/sandbox-testing)<a href="https://agentmods.dev/skills/paddlehq/paddle-agent-skills/sandbox-testing"><img src="https://agentmods.dev/badge/skills/paddlehq/paddle-agent-skills/sandbox-testing/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/paddlehq/paddle-agent-skills/sandbox-testing"><img src="https://agentmods.dev/badge/skills/paddlehq/paddle-agent-skills/sandbox-testing.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.02639 |
| Opus 5 | $0.00017 | $0.01319 |
| Sonnet 5 | $0.00007 | $0.00528 |
| Haiku 4.5 | $0.00003 | $0.00264 |
Grade A, and why
paddle-sandbox-testing 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 10d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test a Paddle integration in the sandbox
When to use this skill
Use this skill when verifying a Paddle integration before going live — running real-looking checkouts, triggering webhook events, and exercising subscription state changes without taking real money. Covers sandbox configuration, test card numbers, the webhook simulator (single events and scenarios), local development with public tunnels, and the differences between sandbox and live behavior that bite people in production.
This skill is the safety net for everything else. Apply it alongside checkout-web, webhooks, and subscription-sync whenever you ship — sandbox testing is the cheapest way to catch integration bugs.
Sandbox vs production at a glance
Paddle gives you two completely separate environments:
| Sandbox | Production | |
|---|---|---|
| Purpose | Development and testing | Real customers, real money |
| API base | sandbox-api.paddle.com |
api.paddle.com |
| Dashboard | sandbox-vendors.paddle.com |
vendors.paddle.com |
| API keys | Separate set | Separate set |
| Client tokens | Separate set | Separate set |
| Notification destinations | Separate set | Separate set |
| Products / prices / customers | Separate (none synced) | — |
| Cards accepted | Test cards only (real cards rejected) | Real cards |
| Adjustments / refunds | Auto-approved | Manual approval |
| Tax | Calculated but not collected | Real tax handling |
| Domain approval | No approval required (any domain) | Manual approval per domain |
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.
- 10d ago First seen · 182 lines · 34 tokens per session scan A 062270a7172e
paddle-sandbox-testing is a skill published in the GitHub repository PaddleHQ/paddle-agent-skills (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 34 tokens to every session and 2,639 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
synthetic-monitoring
AI-powered synthetic monitoring skill for e-commerce websites. Designs automated user journey tests for add-to-cart, checkout, and payment flows with alerting rules and performance baselines.
visual-regression-testing
AI-powered visual regression testing skill for e-commerce websites. Designs screenshot comparison workflows, mobile/desktop visual checks, and change detection alerts to prevent conversion-killing UI bugs.
smoke-test-critical-paths
Quick Reference - Load this first for fast context (2KB).
payment-testing
Test payment and checkout flows end to end against PSP sandboxes — Stripe first, with the general pattern for Adyen/Braintree/PayPal. Covers Stripe test-mode card numbers and their decline codes, the 3DS/SCA challenge flow and its nested-iframe handling in Playwright, test clocks for subscription/billing-cycle…
spree-testing
Use when the user is writing or running automated tests for a Spree app — model specs, controller specs, API integration tests, admin feature specs, factories, fixtures. Covers RSpec + Factory Bot + Capybara (Spree's stack — NOT Minitest + fixtures), the spreedevtools gem, pulling in Spree's own factories, the shared…
shop
Guest shopping journey QA for WooCommerce stores — catalog to checkout, never placing an order.