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 IAPro-Community/Orquestrador-Maestro --skill skill-stripe-integrationgit clone --depth 1 https://github.com/IAPro-Community/Orquestrador-MaestroWrote 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/iapro-community/orquestrador-maestro/skill-stripe-integration)<a href="https://agentmods.dev/skills/iapro-community/orquestrador-maestro/skill-stripe-integration"><img src="https://agentmods.dev/badge/skills/iapro-community/orquestrador-maestro/skill-stripe-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/iapro-community/orquestrador-maestro/skill-stripe-integration"><img src="https://agentmods.dev/badge/skills/iapro-community/orquestrador-maestro/skill-stripe-integration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00037 | $0.00754 |
| Opus 5.5 | $0.00015 | $0.00302 |
| Sonnet 5.5 | $0.00007 | $0.00151 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
skill-stripe-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 1mo 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
skill-stripe-integration
Workflow
- Inspect existing backend boundaries, env naming, Stripe SDK usage, price/product mapping, subscription tables, and entitlement tables.
- Keep Stripe secret keys and webhook secrets in server-only code. Browser code may only receive publishable keys and backend-created session/portal URLs.
- Create Checkout or Portal sessions on the backend with authenticated actor context and stable metadata.
- Verify webhook signatures with the raw request body before parsing business data.
- Deduplicate events by Stripe event ID and store relevant Stripe IDs for support: customer, checkout session, subscription, invoice, payment intent, price, and product.
- Sync product access from backend subscription/payment state and local entitlement policy, not from the success redirect alone.
- Validate with Stripe test mode, CLI/webhook events, and the project build/typecheck.
Guardrails
- Use official Stripe libraries for webhook signature verification.
- Configure the framework route so the webhook endpoint receives the raw body.
- Listen only to required event types.
- Return a 2xx quickly; move heavy processing to a queue/job when possible.
- Re-fetch critical Stripe objects when event ordering or stale local state matters.
- Keep plan and entitlement rules in local product tables; Stripe prices/products are billing evidence, not the whole access model.
- Never log secret keys, webhook secrets, complete card/payment details, or unnecessary PII.
API Versioning
- Pin the Stripe API version in the server SDK/client or endpoint configuration instead of relying silently on the account default.
- The current Stripe API version at verification time is
2026-02-25.clover; treat this as a maintenance reference, not a reason to upgrade production automatically. - Review the Stripe changelog and run a test-mode webhook migration before adopting a new breaking release. Monthly releases within a major release are designed to be backward-compatible, but twice-yearly major releases can require code changes.
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.
- 1mo ago First seen · 67 lines · 37 tokens per session scan A 4070dad1c303
skill-stripe-integration is a skill published in the GitHub repository IAPro-Community/Orquestrador-Maestro (63 stars, last pushed today), licensed Apache-2.0. It adds 37 tokens to every session and 754 once invoked, about $0.0001 per session on Opus 5.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
payment-reconciliation-automation
Automate payment reconciliation across Stripe, PayPal, and bank accounts with exception handling, automated matching rules, and discrepancy alerting.
stripe-integration
Build secure payment flows with Stripe — Payment Intents, subscription billing, webhook handling, and European SCA compliance for card payments.
paypal-integration
Add PayPal, Venmo, and Pay Later buttons to your store using the PayPal Commerce Platform SDK with Express Checkout for one-tap buying.
sumup
Implement SumUp checkout flows end-to-end. Use when writing or reviewing SumUp Checkouts API calls, Card Widget mounts, Hosted Checkout setup, recurring tokenization, Terminal SDK / Cloud API reader checkouts, or 3DS / webhook handling.
payram-checkout-integration
Integrate PayRam checkout flow into web applications. Generate payment links, embed payment pages, handle redirects, and process payment confirmations. Supports Express, Next.js, FastAPI, Laravel, Gin, Spring Boot. Use when adding crypto checkout to e-commerce, building payment forms, implementing deposit flows, or…
jpm-merchant-integrations
Implement J.P. Morgan Payments API integrations in a merchant project once OAuth authentication is in place. Use this skill after a merchant has completed JPM onboarding and wired up authentication (typically right after jpm-oauth) and is ready to integrate one of the supported APIs — Checkout, Online Payments…