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 agentmods add skills/coderadius-ai/coderadius/retry-paymentnpx skills add coderadius-ai/coderadius --skill retry-paymentgit clone --depth 1 https://github.com/coderadius-ai/coderadiusWhat 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 | $0.00019 | $0.00101 |
| Opus 5 | $0.00010 | $0.00051 |
| Sonnet 5 | $0.00004 | $0.00020 |
| Haiku 4.5 | $0.00002 | $0.00010 |
Grade A, and why
retry-payment 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 2d 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
Retry Payment
When a payment fails with a retryable error:
- Generate an idempotency key from the order ID and attempt number
- Apply exponential backoff with jitter (base 500ms, max 30s)
- Log each retry attempt with the correlation ID
- After 3 failed attempts, emit a payment.failed domain event
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.
- 2d ago First seen · 14 lines · 19 tokens per session scan A daee82073a05
retry-payment is a skill published in the GitHub repository coderadius-ai/coderadius (24 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 101 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-08-30.
Other skills, from other repositories
payments
This skill should be used when adding payments, subscriptions, billing, or pricing to a SaaS — Stripe integration, checkout, plans, the customer portal, webhooks, or deciding a pricing model. Trigger phrases include "add Stripe", "accept payments", "add a subscription", "charge users", "pricing tiers", "checkout"…
stack-stripe
Stripe platform knowledge overlay for the ETYB team. Loads when work involves the Stripe ecosystem — Payments, Checkout, Elements, Billing, Subscriptions, Meter API, Customer Portal, Connect, Treasury, Issuing, Identity, Tax, Radar, Terminal, Climate, Atlas, Sigma, Data Pipeline, Capital, Financial Connections, Link…
ghl-billing
GoHighLevel billing — invoices, estimates, payments, products, orders, subscriptions, coupons, and pricing. Use when the user asks about invoices, estimates, payments, products, orders, charges, or subscriptions in GoHighLevel.
connect-recommend
Use this skill when the user asks about Stripe Connect configuration, charge patterns, Dashboard access, or how to get started with Connect, is building a marketplace, platform, multi-vendor store, gig platform, or subscription platform, needs to pay out sellers, vendors, or providers, mentions split payments, revenue…
stripe
Emulated Stripe API for local development and testing. Use when the user needs to process payments locally, test checkout flows, create customers, manage products and prices, handle payment intents, work with webhooks, or use the Stripe SDK without hitting real Stripe servers. Triggers include "Stripe API", "emulate…
create-payment-credential
Gets secure, one-time-use payment credentials (cards, tokens) from a Link wallet so agents can complete purchases on behalf of users. Use when the user says "get me a card", "buy something", "pay for X", "make a purchase", "I need to pay", "complete checkout", or asks to transact on any merchant site. Use when the…