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.
git 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/rules/paddlehq/paddle-agent-skills/paddle-integration)<a href="https://agentmods.dev/rules/paddlehq/paddle-agent-skills/paddle-integration"><img src="https://agentmods.dev/badge/rules/paddlehq/paddle-agent-skills/paddle-integration.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.1 | $0.00380 | $0.00380 |
| Opus 5 | $0.00190 | $0.00190 |
| Sonnet 5 | $0.00076 | $0.00076 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
paddle-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 8d 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
Paddle integration rules
When writing or modifying code that integrates with Paddle:
- Always check current Paddle documentation via the paddle-docs MCP server before suggesting code. Do not rely on training data — the API and SDK evolve frequently.
- When calling the Paddle API MCP (
paddle-sandboxorpaddle-live), always runsearchbeforeexecuteto confirm method names and parameter shapes. Don't infer from SDK knowledge — the SDK is camelCase end-to-end, but the MCP uses camelCase method paths (client.clientTokens.create) with snake_case body params and response fields (tax_category,product_id,unit_price). - Default to
paddle-sandboxfor development. Only usepaddle-liveafter the user has explicitly opted into operating on real data. - Prefer the official Paddle SDK for the language in use (paddle-node-sdk, paddle-python-sdk, paddle-go-sdk, paddle-php-sdk) over raw HTTP calls.
- All development uses the sandbox environment. Sandbox API keys contain
_sdbx; sandbox client-side tokens are prefixed withtest_. - Always verify webhook signatures before acting on the payload. In Node, use
paddle.webhooks.unmarshal(). In Python, useVerifier().verify(). In Go, usepaddle.NewWebhookVerifier(). In PHP, use(new Verifier())->verify(). - For destructive account changes (updating prices, archiving products), ask for explicit confirmation before calling destructive operations via
execute, especially onpaddle-live. - Use environment variables for API keys and webhook secrets. Never inline credentials into code.
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.
- 8d ago First seen · 19 lines · 380 tokens per session scan A ff6efcdb8c95
paddle-integration is a cursor rule published in the GitHub repository PaddleHQ/paddle-agent-skills (6 stars, last pushed 29d ago), licensed Apache-2.0. It adds 380 tokens to every session, about $0.0019 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 cursor rules, from other repositories
mena-payment-guardian
Use when building or reviewing Arab/MENA payment or BNPL flows with Paymob, FawryPay, Geidea, PayTabs, Tap Payments, MyFatoorah, HyperPay, Moyasar, Amazon Payment Services, EasyKash, Kashier, PaySky, Tabby, Tamara, valU, Souhoola, callbacks, webhooks, HMAC, SecureHash, redirects, refunds, captures, or payment secrets.
stripe
Stripe payment integration, webhooks, checkout, and subscriptions.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.