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/nathanimphilipos/synergos-grcWrote 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/commands/nathanimphilipos/synergos-grc/audit-prep)<a href="https://agentmods.dev/commands/nathanimphilipos/synergos-grc/audit-prep"><img src="https://agentmods.dev/badge/commands/nathanimphilipos/synergos-grc/audit-prep/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/commands/nathanimphilipos/synergos-grc/audit-prep"><img src="https://agentmods.dev/badge/commands/nathanimphilipos/synergos-grc/audit-prep.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.00009 | $0.00697 |
| Opus 5 | $0.00005 | $0.00349 |
| Sonnet 5 | $0.00002 | $0.00139 |
| Haiku 4.5 | $0.00001 | $0.00070 |
Grade A, and why
audit-prep 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.
This is a copy
100% identical to audit-prep — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/grc:audit-prep
Audit preparation checklists and guidance by audit type.
Usage
/grc:audit-prep [audit-type]
Arguments
- audit-type: The type of audit to prepare for. Accepts:
3pao/fedramp— FedRAMP 3PAO assessment (initial or annual)soc2— SOC 2 Type I or Type II auditiso/iso27001— ISO 27001 certification (Stage 1/2 or surveillance)pci/pcidss— PCI DSS QSA assessmentinternal— Internal auditgap— Readiness / gap analysis (redirects to/grc:gap-analysis)
Examples
/grc:audit-prep 3pao
/grc:audit-prep soc2
/grc:audit-prep iso
/grc:audit-prep pci
/grc:audit-prep internal
Behavior
When invoked:
-
Identify the audit type from the argument.
-
Read the appropriate audit reference file from
audits/:3pao→audits/3pao-assessment.mdsoc2→audits/soc2-audit.mdiso→audits/iso-certification.mdpci→audits/pci-qsa.mdinternal→audits/internal-audit.md
-
Present a structured preparation guide with:
- Audit overview and timeline
- Pre-audit checklist (documents, evidence, systems)
- Phase-by-phase walkthrough
- Evidence requirements organized by control area
- Common findings and how to avoid them
- Day-of logistics (who needs to be available, war room setup)
- Post-audit activities (remediation, POA&M entry)
-
If no audit type provided, show a comparison table of audit types and ask which to prepare for.
Output Format
## Audit Preparation: [Audit Type]
### Overview
- **Assessor**: [Who performs the audit]
- **Duration**: [Typical timeline]
- **Output**: [Deliverables]
- **Frequency**: [How often]
### Pre-Audit Checklist
#### Documents Required
- [ ] [Document 1]
- [ ] [Document 2]
#### Evidence to Prepare
- [ ] [Evidence category 1]
- [ ] [Evidence category 2]
#### Systems/Access
- [ ] [System access needed]
### Phase Walkthrough
1. **[Phase 1]**: [Description, duration, activities]
2. **[Phase 2]**: [Description, duration, activities]
### Common Findings to Address Proactively
| Finding | Control Area | Prevention |
|---------|-------------|------------|
### Day-Of Logistics
- [Logistics item 1]
- [Logistics item 2]
### Post-Audit
- [Post-audit activity 1]
- [Post-audit activity 2]
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 · 99 lines · 9 tokens per session scan A ba0db0c2d22c
audit-prep is a command published in the GitHub repository nathanimphilipos/synergos-grc (5 stars, last pushed 6mo ago), licensed MIT. It adds 9 tokens to every session and 697 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to audit-prep, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
voice-compliance
Voice/telephony compliance check — invokes voice-ai-reviewer to produce TM-voice-{slug}.md with TCPA, STIR/SHAKEN, state recording-consent, EU AI Act Art. 50, and synth-voice deepfake-law gaps.
review-policy
Review a policy document for structure, coverage, and language quality.
at-dsgvo
You are helping an enterprise architect generate an Austrian Data Protection Assessment — the Austrian-specific GDPR layer applied by the Datenschutzbehörde (DSB) under the Datenschutzgesetz (DSG 2018, BGBl. I Nr. 165/1999 as amended). Run this after /arckit:eu-rgpd to add Austrian obligations that go beyond the EU…
au-pspf
You are an enterprise architect generating a Protective Security Policy Framework (PSPF) compliance assessment for an Australian Government entity or contractor handling government information.