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 kensaurus/cursor-kenji --skill audit-payment-systemgit clone --depth 1 https://github.com/kensaurus/cursor-kenjiWrote 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/kensaurus/cursor-kenji/audit-payment-system)<a href="https://agentmods.dev/skills/kensaurus/cursor-kenji/audit-payment-system"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/audit-payment-system/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/kensaurus/cursor-kenji/audit-payment-system"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/audit-payment-system.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00066 | $0.05065 |
| Opus 5.5 | $0.00026 | $0.02026 |
| Sonnet 5.5 | $0.00013 | $0.01013 |
| Haiku 4.5 | $0.00007 | $0.00507 |
Grade A, and why
audit-payment-system 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.
How it starts
The opening of the file, as written. The whole thing — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
audit-payment-system — Money-Movement Correctness & Compliance Audit
Degree of freedom: MIXED — Scope, matrix, and severity [HIGH freedom];
Phase 0 detection searches [LOW freedom — run exactly]. Do not write
exploit or payment-fraud PoCs — quote the missing control, never a replay
or spoof recipe.
Read-only. Assess and prioritize; do not change code. Payment code is a
STOP-and-confirm surface — findings feed a human-reviewed remediation run at
high effort with a fresh-context reviewer. Delegations: per-call resilience → audit-resilience;
PCI/secrets/authz → audit-security; ledger schema → audit-db-schema;
outbox/saga structure → audit-backend-architecture; append-only
integrity → plan-data-integrity; Stripe integration → the Stripe plugin
skills. This skill owns payment-domain correctness.
Payment failures are silent: a retried charge is a double-charge, a lost ledger write is vanished money, a logged PAN is PCI liability, an unverified webhook is an untrusted "paid". Three pillars: idempotency, a double-entry ledger (when in scope), reconciliation — plus PCI DSS v4.0.1 and webhooks as source of truth (never trust the sync API response alone).
Core principle — earn each control by scope; every gap is money or liability
Not every app needs an in-house double-entry ledger. Stripe Checkout offloads ledger, settlement, and most PCI — flagging "no double-entry ledger" there is noise. Idempotency, webhook verification, state sync, and tokens-only apply to everyone who moves money. Gate depth by scope (Phase 0). Critical = a customer is charged twice, money is lost/unaccounted, or card data is exposed. There is no "low severity" for a double-charge.
How to reason — Observe → Interpret → Classify → Severity
- Observe — quote the mutation/webhook/ledger
file:line(or "searched, none found") - Interpret — what money or liability path breaks if that control is missing?
- Classify — Implemented / Partial / Missing / N/A (tier reason); control id (A1–G4)
- Severity — double-charge, lost money, or PAN/CVV exposure = Critical; P2-only rows are N/A on P0
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 · +1 lines · -10 tokens per session 64f422b002bc
- 1mo ago First seen · 268 lines · 76 tokens per session scan A c9ac7df63a99
audit-payment-system is a skill published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 26d ago), licensed MIT. It adds 66 tokens to every session and 5,065 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
sonicg-update-in-app-billing
OrbitalSonic Gemini Skill: Migrate existing orbitalsonic SonicInApp (https://github.com/orbitalsonic/SonicInApp) from v3.x to v4.0.0 — catalog bump, remove listeners, singleton BillingManager, Flow/suspend API, offerId threading. Use when upgrading SonicInApp/inappbilling, Play Billing 9 migration, legacy…
ui-design
Create distinctive, production-grade web interfaces with high design quality using Tailwind CSS. Use for building UI components, pages, dashboards, apps, and web applications. Generates crafted, polished code that avoids generic AI aesthetics.
code-review-codex
Final-gate code review via Codex CLI (codex-5.3, xhigh). Finds bugs, security issues, and regressions before commit. No edits — findings report only.
summarizer
Summarize a YouTube video or podcast episode and save the summary as a structured note in NotePlan under '3 Resources/Podcasts, YT/'. Use this skill whenever the user shares a YouTube link and wants it summarized, noted, or saved — or says things like 'summarize this', 'add this to my notes', 'save this podcast'…
yt-transcript
Fetch YouTube video transcripts and load them into context for further processing. Use this skill whenever the user shares a YouTube URL or video ID and wants to work with the video's content — summarizing, extracting insights, answering questions about it, translating, or feeding it into another workflow. Also…
codex-review
Run code reviews with the Codex CLI, prioritizing bugs, regressions, security risks, and missing tests. Use when the user asks for code review, PR review, diff review, or commit-range review via codex.