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 rahmanef63/si-coder-agent --skill sc-stripegit clone --depth 1 https://github.com/rahmanef63/si-coder-agentWrote 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/rahmanef63/si-coder-agent/sc-stripe)<a href="https://agentmods.dev/skills/rahmanef63/si-coder-agent/sc-stripe"><img src="https://agentmods.dev/badge/skills/rahmanef63/si-coder-agent/sc-stripe/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/rahmanef63/si-coder-agent/sc-stripe"><img src="https://agentmods.dev/badge/skills/rahmanef63/si-coder-agent/sc-stripe.svg" alt="Reviewed on agentmods" width="80" 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 Data Exfiltration · line 46 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00052 | $0.00564 |
| Opus 5.5 | $0.00021 | $0.00226 |
| Sonnet 5.5 | $0.00010 | $0.00113 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
sc-stripe 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.
What it actually says
/sc-stripe — Stripe (STUB)
Status: boilerplate only. No working scripts yet.
Scope when implemented
- Create/update Products + Prices idempotently from a config file
- Register webhook endpoint at
https://api-<domain>/webhook/stripeand capture the signing secret - Generate a restricted API key (least-privilege) for the runtime, distinct from the dashboard key
- Configure the Customer Portal session URL
- Smoke-test with a Stripe test-mode checkout link
Env vars
| Var | Purpose |
|---|---|
STRIPE_SECRET_KEY |
sk_test_... or sk_live_... (server-side) |
STRIPE_PUBLISHABLE_KEY |
pk_test_... or pk_live_... (client-side) |
STRIPE_WEBHOOK_SECRET |
whsec_... — captured after webhook registration |
Suggested file layout
sc-stripe/
├── SKILL.md
└── scripts/
├── products.js # idempotent product/price upsert from config
├── webhook.js # register endpoint, capture whsec
├── portal.js # customer portal config
└── restricted-key.js # least-privilege key for runtime
Implementation notes
- API base:
https://api.stripe.com/v1 - Auth:
Authorization: Bearer <STRIPE_SECRET_KEY>+Stripe-Version: 2024-12-18.acacia - Bodies are
application/x-www-form-urlencoded, NOT JSON. - Idempotency: pass
Idempotency-Key: <uuid>header to avoid duplicate products on retry. - Convex integration: see
sc-convexforpaymentsschema +http.ts/webhook/striperoute example.
What ships with it
1 file 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.
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 Changed · +6 lines 82a0640f8eec
- 1mo ago First seen · 45 lines · 52 tokens per session scan A e1ea99da2ee2
sc-stripe is a skill published in the GitHub repository rahmanef63/si-coder-agent (13 stars, last pushed 3d ago), licensed MIT. It adds 52 tokens to every session and 564 once invoked, about $0.0002 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
medusa-development
Best practices for building commerce applications with Medusa v2, the headless e-commerce framework. Use when defining Medusa data models, writing workflows and steps with the Workflow SDK, creating API routes or subscribers, building module services that extend MedusaService, throwing MedusaError, or customizing the…
paypal-routing
PayPal payments, subscriptions, checkout, invoices, disputes, webhooks, BNPL, Venmo, SDK, v5, v6, Fastlane, Braintree Fastlane, braintree-web, accelerated guest checkout. Routes PayPal developer questions to the right command or reference file.
prestashop-module-development
Complete PrestaShop module development workflow using modern architecture and best practices. Use when: creating new PrestaShop modules, updating legacy modules to modern code, implementing hooks and actions, setting up module configuration pages, adding front office features, handling database operations…
convex-http-actions
External API integration and webhook handling including HTTP endpoint routing, request/response handling, authentication, CORS configuration, and webhook signature validation.
convex-agents
Building AI agents with the Convex Agent component including thread management, tool integration, streaming responses, RAG patterns, and workflow orchestration.
convex-component-authoring
How to create, structure, and publish self-contained Convex components with proper isolation, exports, and dependency management.