payment-failure-audit

payment-failure-audit is a skill for Claude Code, Codex from appeeky/stripe-skills. It costs 55 tokens per session (493 once invoked), scanned A, original, MIT.

An audit guide for examining failed Stripe payments, including declined charges, failed payment attempts, invoice failures, and decline reasons. Stripe is a payment service, and a decline code describes why a payment was not accepted.

In plain words
What is it for?
Use it to review failed charges and PaymentIntents, find open subscription invoices, group failures by reason or card details, and assess payment failure rates.
Why use it?
It groups payment failures into patterns that can explain lost payments. This helps distinguish issues such as insufficient funds, expired cards, generic declines, and required authentication.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to review failed charges and PaymentIntents, find open subscription invoices, group failures by reason or card details, and assess payment failure rates.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/appeeky/stripe-skills/payment-failure-audit
Install

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.

Any agent
npx skills add appeeky/stripe-skills --skill payment-failure-audit
Clone the repo
git clone --depth 1 https://github.com/appeeky/stripe-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for payment-failure-audit

README.md
[![agentmods](https://agentmods.dev/badge/skills/appeeky/stripe-skills/payment-failure-audit/github.svg)](https://agentmods.dev/skills/appeeky/stripe-skills/payment-failure-audit)
Your own site
<a href="https://agentmods.dev/skills/appeeky/stripe-skills/payment-failure-audit"><img src="https://agentmods.dev/badge/skills/appeeky/stripe-skills/payment-failure-audit/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.

agentmods 80×15 button for payment-failure-audit

Your own site · 80×15
<a href="https://agentmods.dev/skills/appeeky/stripe-skills/payment-failure-audit"><img src="https://agentmods.dev/badge/skills/appeeky/stripe-skills/payment-failure-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 493 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00055 $0.00493
Opus 5 $0.00028 $0.00246
Sonnet 5 $0.00011 $0.00099
Haiku 4.5 $0.00006 $0.00049

Measured 11d ago against content hash c49710db32ce, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

payment-failure-audit 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 11d 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.

skills/payment-failure-audit/SKILL.md · 61 lines

What it actually says

Payment Failure Audit

Stripe MCP Setup

Requires Stripe MCP connected via OAuth or restricted key. Docs: https://docs.stripe.com/mcp

  1. GetMcpTools with server: "user-Stripe" (or plugin-stripe-stripe) before any call
  2. Prefer stripe_api_searchstripe_api_detailsstripe_api_read for list/retrieve
  3. Always paginatelimit: 100, follow has_more with starting_after
  4. Amounts are in cents unless noted
  5. Never expose secret keys in output

Workflow

  1. Recent failed chargesGetCharges with filter or search:
    • search_stripe_resources: charges:status:"failed" (paginate if possible)
  2. Failed PaymentIntentsGetPaymentIntents status requires_payment_method or failed
  3. Open invoicesGetInvoices with status: open and subscription set
  4. Group failures by:
    • outcome.reason / decline code
    • card.funding
    • card.country
    • Wallet vs direct card

Common Decline Reasons

Code / reason Typical fix
insufficient_funds Debit balance — dunning email
card_declined Generic — retry + update PM
expired_card Expiring card email
authentication_required Enable 3DS on setup
Radar block Review Radar rules

Output Template

Payment Failures ([period])

Total failed: [N] | $[amount]
Failure rate: [X]% of attempts

By reason:
| Reason | Count | % |

By card funding:
| funding | Count |

Top recommendations:
1. ...

Link to radar-fraud-rules if blocked or highest risk level appears in outcomes.

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.

  1. 11d ago First seen · 61 lines · 55 tokens per session scan A c49710db32ce

Subscribe to this mod's changes

payment-failure-audit is a skill published in the GitHub repository appeeky/stripe-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 493 once invoked, about $0.0003 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-31.

Related

Other skills, from other repositories

stock-liquidity

Analyze stock liquidity using bid-ask spreads, volume profiles, order book depth, market impact estimates, and turnover ratios via Yahoo Finance data. Use this skill whenever the user asks about liquidity, trading costs, bid-ask spread, market depth, volume analysis, slippage, market impact, turnover ratio, or how…

himself65/finance-skills · 188 tokens

company-valuation

Estimate the intrinsic value of a public company using DCF, relative (peer multiple) and sum-of-parts (SOTP) methods, then triangulate to an implied share price with upside/downside versus the current market price. Use this skill whenever the user asks: "what is AAPL worth", "valuation of NVDA", "fair value of TSLA"…

himself65/finance-skills · 234 tokens

fintel-data

Query Fintel (fintel.io) institutional market intelligence via the REST API at https://api.fintel.io/v1 with FINTELAPIKEY (X-API-KEY header), or the official MCP server at https://mcp.fintel.io/mcp. Read-only data: short interest, borrow rate/fee and shares available to borrow, daily short volume, fails-to-deliver…

himself65/finance-skills · 234 tokens

estimate-analysis

Deep-dive into analyst estimates and revision trends for any stock using Yahoo Finance data. Use when the user wants to understand analyst estimate direction, how EPS or revenue forecasts changed over time, compare estimate distributions, or analyze growth projections across periods. Triggers: "estimate analysis for…

himself65/finance-skills · 195 tokens

earnings-preview

Generate a pre-earnings briefing for any stock using Yahoo Finance data. Use this skill whenever the user wants to prepare for an upcoming earnings report, understand what analysts expect, review a company's beat/miss track record, or get a quick overview before an earnings call. Triggers include: "earnings preview…

himself65/finance-skills · 221 tokens

earnings-recap

Generate a post-earnings analysis for any stock using Yahoo Finance data. Use when the user wants to review what happened after earnings, understand beat/miss results, see stock reaction, or get an earnings recap. Triggers: "AAPL earnings recap", "how did TSLA earnings go", "MSFT earnings results", "did NVDA beat…

himself65/finance-skills · 186 tokens