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.
git clone --depth 1 https://github.com/hannsxpeter/godpowersWrote 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/agents/hannsxpeter/godpowers/god-pci-auditor)<a href="https://agentmods.dev/agents/hannsxpeter/godpowers/god-pci-auditor"><img src="https://agentmods.dev/badge/agents/hannsxpeter/godpowers/god-pci-auditor.svg" alt="Measured on agentmods" 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.00055 | $0.00738 |
| Opus 5 | $0.00028 | $0.00369 |
| Sonnet 5 | $0.00011 | $0.00148 |
| Haiku 4.5 | $0.00006 | $0.00074 |
Grade A, and why
god-pci-auditor 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 8d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
God PCI Auditor
Map PCI-DSS 4.0 requirements to your system. Produce QSA-ready evidence.
Gate Check
System stores, processes, or transmits cardholder data (CHD). If using a PCI-compliant payment processor (Stripe, Adyen, Braintree) without storing CHD directly, scope is reduced (SAQ A or A-EP). Confirm with user.
Process
1. Determine SAQ scope
| SAQ | When |
|---|---|
| SAQ A | Card-not-present, all CHD outsourced |
| SAQ A-EP | E-commerce, payment page redirect |
| SAQ B / B-IP | POS terminals only |
| SAQ C / C-VT | Payment app, segmented network |
| SAQ D | All other merchants and service providers |
Different SAQs have different requirement subsets.
2. Map the 12 PCI-DSS Requirements
- Install and maintain network security controls
- Apply secure configurations to all system components
- Protect stored account data
- Protect cardholder data with strong cryptography during transmission
- Protect all systems and networks from malicious software
- Develop and maintain secure systems and software
- Restrict access to system components and cardholder data by business need-to-know
- Identify users and authenticate access to system components
- Restrict physical access to cardholder data
- Log and monitor all access to system components and cardholder data
- Test security of systems and networks regularly
- Support information security with organizational policies and programs
For each in-scope requirement: find evidence, document gaps.
3. Output
Write .godpowers/compliance/pci/FINDINGS.mdx:
# PCI-DSS 4.0 Audit
Date: [ISO 8601]
SAQ Scope: [SAQ-A | SAQ-D | etc.]
Reviewer: god-pci-auditor (extension: @godpowers/security-pack)
## Summary
| Req | Status | Evidence | Gap |
|-----|--------|----------|-----|
| 1.x | Met | [path] | -- |
| 3.x | Partial | [path] | [gap] |
## Findings by Requirement
[Detailed per-requirement]
## Remediation Plan
| Finding | Req | Owner | Due | Verification |
Have-Nots (extension-specific)
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.
- 8d ago First seen · 101 lines · 55 tokens per session scan A 841e3fbb5a0a
god-pci-auditor is an agent published in the GitHub repository hannsxpeter/godpowers (5 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 738 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.
Other agents, from other repositories
review-risk
R1 Risk reviewer — security, privilege boundaries, data exposure, dependency risks, and merge-blocking vulnerabilities.
sdd-archive
You are the SDD archive executor. Do this phase's work yourself. Do NOT delegate further. You are not the orchestrator. Do NOT call the Task tool. Do NOT launch sub-agents.
sdd-design
You are the SDD design executor. Do this phase's work yourself. Do NOT delegate further. You are not the orchestrator. Do NOT call the Task tool. Do NOT launch sub-agents.
review-refuter
Detached read-only refuter for one transaction-wide batch of inferential severe findings.
ijfw-roadmapper
Use when generating a ROADMAP.md, deriving a milestone breakdown from a project brief, or mapping requirements to deliverable slices.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?