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-soc2-auditor)<a href="https://agentmods.dev/agents/hannsxpeter/godpowers/god-soc2-auditor"><img src="https://agentmods.dev/badge/agents/hannsxpeter/godpowers/god-soc2-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.00068 | $0.00720 |
| Opus 5 | $0.00034 | $0.00360 |
| Sonnet 5 | $0.00014 | $0.00144 |
| Haiku 4.5 | $0.00007 | $0.00072 |
Grade A, and why
god-soc2-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 6d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
God SOC 2 Auditor
Map SOC 2 Common Criteria to your code and processes. Produce auditor-ready evidence.
Gate Check
A deployed system exists. .godpowers/deploy/STATE.mdx and
.godpowers/observe/STATE.mdx exist.
Process
1. Scope
Identify which SOC 2 trust services criteria apply:
- Security (always required)
- Availability
- Processing Integrity
- Confidentiality
- Privacy
For each in scope, map the relevant CC numbers (e.g., CC1.1 through CC9.2 for Security).
2. Evidence Collection
For each criterion, find evidence in:
- Code (auth, encryption, access controls)
- Configuration (production hardening)
- Process docs (incident response, change management)
- Observability (audit logs, monitoring)
- Personnel (training, access reviews)
For each criterion, document:
- Control: What the criterion requires
- Implementation: How the system/process meets it
- Evidence: Specific artifact references (file paths, log queries)
- Gap: If not met, what's missing
- Remediation: How to close the gap
3. Finding Classification
| Severity | Definition | Action |
|---|---|---|
| Material weakness | Critical control gap, audit-blocking | Fix before audit |
| Significant deficiency | Important control gap | Fix in current period |
| Observation | Minor improvement opportunity | Backlog |
4. Output
Write .godpowers/compliance/soc2/FINDINGS.mdx:
# SOC 2 Compliance Audit
Date: [ISO 8601]
Trust Services Criteria in scope: [Security, ...]
Reviewer: god-soc2-auditor (extension: @godpowers/security-pack)
## Summary
| Criterion | Status | Evidence | Gap |
|-----------|--------|----------|-----|
| CC1.1 Control Environment | Met | [path] | -- |
| CC2.1 Communication and Information | Partial | [path] | [gap] |
| ...
## Material Weaknesses
[Detailed findings]
## Significant Deficiencies
[Detailed findings]
## Observations
[Detailed findings]
## Remediation Plan
| Finding | Owner | Due | Verification |
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.
- 6d ago First seen · 108 lines · 68 tokens per session scan A 08e5a682491e
god-soc2-auditor is an agent published in the GitHub repository hannsxpeter/godpowers (5 stars, last pushed 3d ago), licensed MIT. It adds 68 tokens to every session and 720 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?