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 arbazkhan971/godmode --skill complygit clone --depth 1 https://github.com/arbazkhan971/godmodeWrote 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/arbazkhan971/godmode/comply)<a href="https://agentmods.dev/skills/arbazkhan971/godmode/comply"><img src="https://agentmods.dev/badge/skills/arbazkhan971/godmode/comply.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.00031 | $0.02968 |
| Opus 5 | $0.00015 | $0.01484 |
| Sonnet 5 | $0.00006 | $0.00594 |
| Haiku 4.5 | $0.00003 | $0.00297 |
Grade A, and why
comply 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 7d 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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Comply — Compliance & Governance
Activate When
- User invokes
/godmode:comply - User says "are we GDPR compliant?", "audit trail", "privacy review", "compliance check"
- Team builds features handling personal data, health data, or payment data
- Pre-ship check when
/godmode:shipdetects regulated data flows - User needs license compliance audit across dependencies
- Preparing for SOC2 audit or regulatory review
Workflow
Step 1: Define Compliance Scope
Determine which regulations and what code is in scope:
COMPLIANCE SCOPE:
Target: <feature/module/entire project>
Applicable regulations:
- [ ] GDPR (personal data of EU residents)
- [ ] HIPAA (protected health information)
- [ ] SOC2 (service organization controls)
- [ ] PCI-DSS (payment card data)
- [ ] CCPA (California consumer privacy)
- [ ] FERPA (educational records)
- [ ] Other: <specify>
Data classification:
Personal data: <files/modules handling PII>
Sensitive data: <files/modules handling health/financial/auth data>
Public data: <files/modules with non-sensitive data>
Step 2: GDPR Compliance Check
If personal data of EU residents is processed:
Lawful Basis
GDPR — LAWFUL BASIS ASSESSMENT:
| Data Processing Activity | Lawful Basis | Status |
|--|--|--|
| User registration | Consent | COMPLIANT |
| Order processing | Contract | COMPLIANT |
| Marketing emails | Consent | MISSING |
| Analytics tracking | Legitimate int. | REVIEW |
| Fraud detection | Legitimate int. | COMPLIANT |
Data Subject Rights
GDPR — DATA SUBJECT RIGHTS:
| Right | Implemented | Location |
|--|--|--|
| Right to access | YES/NO | <endpoint/UI> |
| Right to rectification | YES/NO | <endpoint/UI> |
| Right to erasure | YES/NO | <endpoint/UI> |
| Right to portability | YES/NO | <endpoint/UI> |
| Right to restrict proc. | YES/NO | <endpoint/UI> |
| Right to object | YES/NO | <endpoint/UI> |
| Automated decision-making | YES/NO/N/A | <endpoint/UI> |
Consent Management
CONSENT IMPLEMENTATION CHECK:
- [ ] Consent is freely given (not bundled with service access)
- [ ] Consent is specific (separate consent per purpose)
- [ ] Consent is informed (clear language, not legalese)
- [ ] Consent is unambiguous (affirmative action, no pre-ticked boxes)
- [ ] Consent is withdrawable (easy opt-out, same effort as opt-in)
- [ ] Consent records stored (who, when, what, version of terms)
- [ ] Under-16 users: parental consent mechanism exists
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.
- 7d ago First seen · 303 lines · 31 tokens per session scan A 21762bcdec94
comply is a skill published in the GitHub repository arbazkhan971/godmode (26 stars, last pushed 9d ago), licensed MIT. It adds 31 tokens to every session and 2,968 once invoked, about $0.0002 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
orca-custom-framework
Creates custom compliance frameworks from existing frameworks, alert lists, or security themes — organizes controls into sections, maps alerts, and pushes the framework to Orca. Suggests creating custom discovery alerts for gaps not covered by existing rules. Use when user asks to create, build, or generate a custom…
hr-payroll
Help HR operations specialists, payroll administrators, and compensation teams understand, design, and run payroll processing, compliance, and payroll-related HR operations. Use when asked to set up a payroll process, run a payroll compliance audit, design a payroll calendar, handle a payroll discrepancy, build a…
hr-mergers-acquisitions
Help HR leaders manage the people dimensions of M&A transactions — due diligence, deal structuring input, and pre-close workforce planning. Use when asked to conduct HR due diligence for an acquisition, assess culture fit before a merger, plan workforce implications of a deal, build an M&A HR integration plan, or…
hr-retirement-benefits
Help compensation and benefits teams design, communicate, and administer retirement and pension benefits. Use when asked to design our retirement benefit offering, explain 401(k)/pension options to employees, compare retirement plan providers, communicate a retirement plan change, or help an employee understand their…
hr-audit
Help HR and compliance teams plan and conduct HR audits, including policy compliance reviews, I-9/documentation audits, pay equity checks, and process audits. Use when asked to conduct an HR audit, audit HR compliance, review personnel files for compliance, build an HR audit checklist, or similar HR audit tasks.
hr-offboarding
Help HR teams design and execute effective offboarding processes for voluntary and involuntary departures. Use when asked to create an offboarding checklist, conduct exit interviews, manage employee separations, handle involuntary terminations, build an alumni program, or similar departure management tasks.