Borrowing it
Nothing to install: this file belongs to cohen-liel/hivemind. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/cohen-liel/hivemind/main/.claude/skills/stripe-payments/SKILL.mdgit clone --depth 1 https://github.com/cohen-liel/hivemindWrote 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/cohen-liel/hivemind/stripe-payments)<a href="https://agentmods.dev/skills/cohen-liel/hivemind/stripe-payments"><img src="https://agentmods.dev/badge/skills/cohen-liel/hivemind/stripe-payments/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/cohen-liel/hivemind/stripe-payments"><img src="https://agentmods.dev/badge/skills/cohen-liel/hivemind/stripe-payments.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.00029 | $0.01614 |
| Opus 5 | $0.00015 | $0.00807 |
| Sonnet 5 | $0.00006 | $0.00323 |
| Haiku 4.5 | $0.00003 | $0.00161 |
Grade A, and why
stripe-payments 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.
How it starts
The opening of the file, as written. The whole thing — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stripe Payments Patterns
Setup
# payments.py
import stripe
from fastapi import HTTPException
stripe.api_key = settings.STRIPE_SECRET_KEY
WEBHOOK_SECRET = settings.STRIPE_WEBHOOK_SECRET
// lib/stripe.ts
import Stripe from 'stripe'
export const stripe = new Stripe(process.env.STRIPE_SECRET_KEY!, {
apiVersion: '2024-06-20',
})
One-Time Payment (Checkout Session)
@router.post("/create-checkout-session")
async def create_checkout_session(user: User = Depends(get_current_user)):
session = stripe.checkout.Session.create(
payment_method_types=["card"],
line_items=[{
"price": "price_xyz123", # Price ID from Stripe dashboard
"quantity": 1,
}],
mode="payment",
success_url=f"{BASE_URL}/success?session_id={{CHECKOUT_SESSION_ID}}",
cancel_url=f"{BASE_URL}/cancel",
customer_email=user.email,
metadata={"user_id": str(user.id)},
)
return {"checkout_url": session.url}
// Next.js API route
export async function POST(req: Request) {
const session = await stripe.checkout.sessions.create({
payment_method_types: ['card'],
line_items: [{ price: 'price_xyz123', quantity: 1 }],
mode: 'payment',
success_url: `${process.env.NEXT_PUBLIC_URL}/success`,
cancel_url: `${process.env.NEXT_PUBLIC_URL}/cancel`,
})
return Response.json({ url: session.url })
}
Subscriptions
@router.post("/create-subscription")
async def create_subscription(
price_id: str,
user: User = Depends(get_current_user),
):
# Create or retrieve Stripe customer
if not user.stripe_customer_id:
customer = stripe.Customer.create(
email=user.email,
metadata={"user_id": str(user.id)},
)
await db.user.update(user.id, stripe_customer_id=customer.id)
customer_id = customer.id
else:
customer_id = user.stripe_customer_id
session = stripe.checkout.Session.create(
customer=customer_id,
payment_method_types=["card"],
line_items=[{"price": price_id, "quantity": 1}],
mode="subscription",
success_url=f"{BASE_URL}/dashboard?upgraded=1",
cancel_url=f"{BASE_URL}/pricing",
)
return {"checkout_url": session.url}
@router.post("/cancel-subscription")
async def cancel_subscription(user: User = Depends(get_current_user)):
subscription = stripe.Subscription.retrieve(user.stripe_subscription_id)
# Cancel at period end (not immediately)
stripe.Subscription.modify(
user.stripe_subscription_id,
cancel_at_period_end=True,
)
return {"message": "Subscription will cancel at end of billing period"}
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 · 229 lines · 29 tokens per session scan A f43817925536
stripe-payments is a skill published in the GitHub repository cohen-liel/hivemind (107 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 1,614 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
shopify-apps
Shopify app development - Remix, Admin API, checkout extensions.
baselinker-webhooks
Receive BaseLinker (Base.com) webhooks. Use when building a BaseLinker order or warehouse callback receiver, because BaseLinker is not a normal webhook source: deliveries arrive as HTTP HEAD requests with NO body, the entire payload is in the query string (observed params: orderid, state), there is NO signature…
recharge-webhooks
Receive and verify Recharge (subscription commerce) webhooks. Use when setting up Recharge webhook handlers, debugging X-Recharge-Webhook-Signature or legacy X-Recharge-Hmac-Sha256 signature verification, or handling subscription events like charge/paid, charge/failed, subscription/created, subscription/cancelled, and…
bigcommerce-webhooks
Receive and verify BigCommerce webhooks. Use when setting up BigCommerce webhook handlers, debugging Standard Webhooks signature verification, or handling store events like store/order/created, store/order/statusUpdated, store/product/updated, or store/cart/abandoned.
commercelayer-webhooks
Receive and verify Commerce Layer webhooks. Use when setting up Commerce Layer webhook handlers, debugging X-CommerceLayer-Signature verification, or handling commerce events like orders.place, orders.approve, orders.pay, or shipments.ship.
mollie-webhooks
Receive and handle Mollie webhooks. Use when setting up Mollie webhook handlers, understanding why Mollie webhooks are not signed, or handling payment status changes like paid, expired, failed, canceled, or authorized. Teaches the fetch-to-confirm pattern: the webhook only sends a payment id, so you fetch the payment…