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 fusengine/agents --skill laravel-stripe-connectgit clone --depth 1 https://github.com/fusengine/agentsWrote 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/fusengine/agents/laravel-stripe-connect)<a href="https://agentmods.dev/skills/fusengine/agents/laravel-stripe-connect"><img src="https://agentmods.dev/badge/skills/fusengine/agents/laravel-stripe-connect.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 235 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00029 | $0.02061 |
| Opus 5 | $0.00015 | $0.01030 |
| Sonnet 5 | $0.00006 | $0.00412 |
| Haiku 4.5 | $0.00003 | $0.00206 |
Grade A, and why
laravel-stripe-connect 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 3d 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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Laravel Stripe Connect
Agent Workflow (MANDATORY)
Before ANY implementation, spawn 3 agents in parallel, one Agent call each with a name:
- fuse-ai-pilot:explore-codebase - Check existing payment setup, Seller model
- fuse-ai-pilot:research-expert - Verify latest Stripe Connect docs via Context7
- mcp__context7__query-docs - Query specific patterns (account types, payment flows)
After implementation, run fuse-ai-pilot:sniper for validation.
Overview
Stripe Connect enables platforms and marketplaces to accept payments and pay out sellers/service providers.
| Use Case | Example | This Skill |
|---|---|---|
| Marketplace | Etsy, eBay | ✅ Yes |
| On-demand services | Uber, DoorDash | ✅ Yes |
| Crowdfunding | Kickstarter | ✅ Yes |
| SaaS with payouts | Substack, Teachable | ✅ Yes |
| Simple SaaS | Netflix, Notion | ❌ Use billing |
Key Difference: Billing vs Connect
| Aspect | Laravel Cashier | Stripe Connect |
|---|---|---|
| Money flow | Customer → You | Customer → Seller (via you) |
| Accounts | 1 Stripe account | Platform + N seller accounts |
| Use case | Subscriptions | Multi-party payments |
| Complexity | Simple | Complex |
Critical Rules
- Verify seller identity - KYC required before payouts
- Handle negative balances - Platform liable if seller can't cover refunds
- Webhook-driven - Never trust client-side for payment confirmation
- Store account IDs - Always persist
stripe_account_idon sellers - Test with test mode - Use test account IDs before production
- Understand liability - Know who pays for disputes per account type
What ships with it
14 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.
- references/account-types.md 2.3 KB
- references/compliance.md 2.7 KB
- references/fees-commissions.md 2.4 KB
- references/onboarding.md 2.5 KB
- references/overview.md 2.1 KB
- references/payment-flows.md 2.4 KB
- references/payouts.md 2.4 KB
- references/refunds-disputes.md 2.9 KB
- references/templates/ConnectRoutes.php.md 4.6 KB
- references/templates/ConnectWebhookHandler.php.md 7.4 KB
- references/templates/MarketplacePaymentController.php.md 8.5 KB
- references/templates/PayoutController.php.md 6.6 KB
- references/templates/Seller.php.md 4.6 KB
- references/templates/SellerOnboardingController.php.md 6.3 KB
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.
- 3d ago Changed 94ec76d49e99
- 5d ago First seen · 246 lines · 29 tokens per session scan A 4c00abf28b52
laravel-stripe-connect is a skill published in the GitHub repository fusengine/agents (25 stars, last pushed 3d ago), licensed MIT. It adds 29 tokens to every session and 2,061 once invoked, about $0.0001 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
paypal-best-practices
PayPal integration guidance, code examples, and best practices. Use for checkout, card fields, BNPL, Pay Later, Venmo, subscriptions, invoicing, disputes, payouts, webhooks, APMs, JS SDK v5, JS SDK v6, createInstance, payment sessions, web components, Fastlane, payment links, donations, 3D Secure, vaulting, iDEAL…
bank-partnership
Assess partner bank compliance requirements — OCC/FDIC expectations, regulatory pass-through.
materiality
Determine significance thresholds for reporting and adjustment decisions.
adjust
Record accruals, deferrals, depreciation, and other period-end adjustments.
audit
Perform a deep-dive review of specific accounts or transactions.
close
Close temporary accounts and transfer balances to retained earnings.