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 Ertinox7711/SGRR-AGI-V2 --skill stripe-disputegit clone --depth 1 https://github.com/Ertinox7711/SGRR-AGI-V2Wrote 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/ertinox7711/sgrr-agi-v2/stripe-dispute)<a href="https://agentmods.dev/skills/ertinox7711/sgrr-agi-v2/stripe-dispute"><img src="https://agentmods.dev/badge/skills/ertinox7711/sgrr-agi-v2/stripe-dispute/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/ertinox7711/sgrr-agi-v2/stripe-dispute"><img src="https://agentmods.dev/badge/skills/ertinox7711/sgrr-agi-v2/stripe-dispute.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.00070 | $0.02943 |
| Opus 5.5 | $0.00028 | $0.01177 |
| Sonnet 5.5 | $0.00014 | $0.00589 |
| Haiku 4.5 | $0.00007 | $0.00294 |
Grade A, and why
stripe-dispute scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -u "$STRIPE_SECRET_KEY:" \ How it starts
The opening of the file, as written. The whole thing — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stripe Dispute Fighter
Build evidence packages and submit counter-disputes to Stripe. Works for any SaaS that uses Stripe + a user database with login/usage logs.
When to Use This Skill
Use this skill when the user:
- Receives a Stripe chargeback notification and wants to fight it
- Provides a dispute ID (
du_*) and asks to "counter" / "rebut" / "fight" it - Asks how to gather evidence for a dispute marked
fraudulent,product_not_received,product_unacceptable, orsubscription_canceled - Wants an activity-log PDF showing a customer used their product
Required Environment Variables
STRIPE_SECRET_KEY=sk_live_... # Stripe restricted/secret key with disputes:write scope
DATABASE_URL=postgres://... # READ-ONLY connection to your app's user database (optional but recommended)
TERMS_URL=https://yoursite.com/terms # URL to your published cancellation/refund policy
EVIDENCE_DIR=~/disputes # Where to save the per-customer evidence folders
Database safety: all queries are SELECT-only. Never let this skill issue UPDATE/DELETE/INSERT.
Inputs
The user provides any of:
- Stripe dispute ID (
du_xxxxx) — preferred - Customer email — skill will look up the dispute
- Charge ID (
ch_xxxxxorpy_xxxxx)
Steps
1. Pull the dispute from Stripe
curl -s -u "$STRIPE_SECRET_KEY:" \
"https://api.stripe.com/v1/disputes/$DISPUTE_ID" | python3 -m json.tool
Extract: amount, reason, charge, evidence_details.due_by, evidence_details.submission_count, status.
If submission_count > 0 the dispute has already been countered — STOP and warn the user.
2. Pull the surrounding context
# Charge → tells you the payment method, risk score, billing details, customer ID
curl -s -u "$STRIPE_SECRET_KEY:" "https://api.stripe.com/v1/charges/$CHARGE_ID"
# Customer → name, email, default payment source
curl -s -u "$STRIPE_SECRET_KEY:" "https://api.stripe.com/v1/customers/$CUSTOMER_ID"
# All invoices for the customer → look for previously-undisputed payments
curl -s -u "$STRIPE_SECRET_KEY:" \
"https://api.stripe.com/v1/invoices?customer=$CUSTOMER_ID&limit=100"
# Subscription (if recurring)
curl -s -u "$STRIPE_SECRET_KEY:" "https://api.stripe.com/v1/subscriptions/$SUB_ID"
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 First seen · 256 lines · 70 tokens per session scan A 858962d038d3
stripe-dispute is a skill published in the GitHub repository Ertinox7711/SGRR-AGI-V2 (1 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 2,943 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-09.
Other skills, from other repositories
kyc-escalation
Write an internal KYC/AML escalation memo: a factual time-stamped trigger description, customer-profile vs activity mismatch analysis, red-flag taxonomy mapping, outstanding information, and a recommendation with rationale. Use when asked to escalate a KYC alert, document an AML concern, write up unusual-activity…
review-contract
Clause-by-clause contract review — inventories key clauses (term, termination, liability cap, indemnity, IP, payment, confidentiality, governing law, auto-renewal), flags deviations from market-standard positions with RED/YELLOW/GREEN severity and verbatim quotes, drafts redline language, and sets negotiation…
expense-review-policy
Review invoices and contracts against accounts-payable policy before human approval.
kyc-doc-parse
Parse an investor or client onboarding packet into structured KYC fields — identity, ownership, control, source of funds, and document inventory. Use as the first step of KYC screening; output feeds the rules engine.
ma-playbook
M&A strategy for acquiring companies or being acquired. Due diligence, valuation, integration, and deal structure. Use when evaluating acquisitions, preparing for acquisition, M&A due diligence, integration planning, or deal negotiation.
prompt-proximity-architecture
Turn an approved measurement charter, ICPs, and buyer jobs into a budget-aware prompt coverage blueprint across proximity bands, aided status, information acts, journey states, roles, locales, evidence grades, partitions, and measurement lanes. Use before prompt wording to define required, optional, and prohibited…