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 sandeepmvl/rails-skills --skill 51-pci-dss-railsgit clone --depth 1 https://github.com/sandeepmvl/rails-skillsWrote 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/sandeepmvl/rails-skills/51-pci-dss-rails)<a href="https://agentmods.dev/skills/sandeepmvl/rails-skills/51-pci-dss-rails"><img src="https://agentmods.dev/badge/skills/sandeepmvl/rails-skills/51-pci-dss-rails/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/sandeepmvl/rails-skills/51-pci-dss-rails"><img src="https://agentmods.dev/badge/skills/sandeepmvl/rails-skills/51-pci-dss-rails.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.00144 | $0.02319 |
| Opus 5 | $0.00072 | $0.01159 |
| Sonnet 5 | $0.00029 | $0.00464 |
| Haiku 4.5 | $0.00014 | $0.00232 |
Grade A, and why
pci-dss-rails 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 12d 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PCI-DSS for Rails
PCI-DSS is the card brands' security standard. If your app touches Primary Account Numbers (PAN), the standard applies. The cheapest path to compliance: don't touch PAN. Use Stripe Elements / Braintree Hosted Fields. The card data never enters your servers. This skill is short by design — the long version is "delegate to a PCI Level 1 provider."
The opinion
NEVER store, transmit, or process PAN (the long card number) on your servers. Use Stripe Elements, Braintree Hosted Fields, or Adyen Drop-In — the iframe approach. Card data goes browser → payment processor, you get a token. This keeps you at SAQ-A scope (the lightest PCI questionnaire). Anything else (SAQ-A-EP, SAQ-D) blows up your compliance scope. NEVER log card numbers anywhere.
What is PCI-DSS?
The Payment Card Industry Data Security Standard, v4.0. 12 requirements, ~300 controls. Annual audit for high-volume merchants; self-assessment questionnaires (SAQ) for smaller ones.
| SAQ | Who | Scope |
|---|---|---|
| SAQ-A | E-commerce, fully outsourced to provider | Lightest — confirm provider compliance, no card data on your servers |
| SAQ-A-EP | E-commerce, partial outsourcing (e.g., you redirect through your server) | Bigger — your servers are in scope |
| SAQ-D | You store / process / transmit PAN | Massive — full 300+ controls, annual audit |
You want SAQ-A. Period.
Pattern 1: Stripe Elements (the right way)
Use the client-confirmation flow — the server creates a PaymentIntent up front, sends its client_secret to the browser, and the browser confirms via Stripe.js (which handles 3DS2/SCA in a Stripe-hosted iframe).
# app/controllers/checkouts_controller.rb — create the intent before rendering.
class CheckoutsController < ApplicationController
def new
@intent = Stripe::PaymentIntent.create(
amount: 1000,
currency: "usd",
automatic_payment_methods: { enabled: true }
)
end
end
<!-- app/views/checkouts/new.html.erb -->
<form id="payment-form" data-client-secret="<%= @intent.client_secret %>">
<div id="payment-element"><!-- Payment Element injects here --></div>
<div id="card-errors" role="alert"></div>
<button type="submit">Pay</button>
</form>
<script src="https://js.stripe.com/v3/"></script>
<script>
const stripe = Stripe('<%= ENV["STRIPE_PUBLISHABLE_KEY"] %>')
const clientSecret = document.querySelector('#payment-form').dataset.clientSecret
const elements = stripe.elements({ clientSecret })
elements.create('payment').mount('#payment-element')
document.querySelector('#payment-form').addEventListener('submit', async (e) => {
e.preventDefault()
const { error } = await stripe.confirmPayment({
elements,
confirmParams: { return_url: window.location.origin + '/checkouts/complete' }
})
if (error) {
document.querySelector('#card-errors').textContent = error.message
}
})
</script>
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.
- 12d ago First seen · 232 lines · 144 tokens per session scan A c18f044e1086
pci-dss-rails is a skill published in the GitHub repository sandeepmvl/rails-skills (21 stars, last pushed 3mo ago), licensed MIT. It adds 144 tokens to every session and 2,319 once invoked, about $0.0007 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
specification-writing
A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.
regulatory-research-fallback
Fallback workflow for regulatory research when web extraction tools fail on government PDFs.
x-scorecard
OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
gesellschaftsrechtliche-satzungen-agb
Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
nda-review
Use when the user uploads or pastes a non-disclosure agreement and asks for review, redline, risk assessment, or a recommendation on whether to sign. Identifies missing standard protections, one-sided or unusual provisions, and operational issues; produces a structured report with severity ratings and citations to…