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 agentmods add commands/fmflurry/settings-opencode/gdpr-reviewgit clone --depth 1 https://github.com/fmflurry/settings-opencodeWhat 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 | $0.00021 | $0.00506 |
| Opus 5 | $0.00010 | $0.00253 |
| Sonnet 5 | $0.00004 | $0.00101 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
gdpr-review 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 2d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GDPR Compliance Review Command
Delegate to the gdpr-specialist agent to conduct a comprehensive GDPR/data-protection compliance audit.
Task
Load the gdpr-compliance skill for reference knowledge and audit checklist. Conduct a full-stack compliance review across:
- Frontend: consent banners, cookies, forms, client-side PII storage, third-party scripts
- Backend: authentication, authorization, input validation, logging (sanitization), data-subject-rights endpoints, legal basis documentation
- Database: PII identification, sensitive-category data, encryption at rest, retention policies, audit logging
- Infrastructure & Stack: data residency, cross-border transfers, processor/vendor contracts, backups, incident response
Produce a tiered, prioritized findings report with:
- Summary of critical, high, medium, and low issues
- GDPR articles and principles breached (with citations)
- Specific file:line evidence for each finding
- Concrete remediation steps for the
coderagent - Compliance scorecard against the audit checklist
Scope
- If
$ARGUMENTSis provided (e.g.,/gdpr-review src/consent): audit that path or feature - If
$ARGUMENTSis empty: audit the entire codebase
$ARGUMENTS
Output Format
Return a structured compliance report per the gdpr-specialist agent specification:
- Severity tiers: CRITICAL → HIGH → MEDIUM → LOW
- Mapping: Each finding → GDPR Article(s) + regulatory risk
- Remediation: Concrete, coder-ready fixes
- Scorecard: Compliance against 6 principles + 8 requirements table
- Disclaimer: Inform that this is informational, not legal advice; consult a DPO/legal counsel for final determination
Legal Disclaimer
This audit is informational guidance based on GDPR articles and CNIL guidance. It is NOT legal advice. For jurisdiction-specific requirements and final compliance determination, consult a Data Protection Officer, legal counsel, or your national data protection authority (CNIL in France: +33 1 53 73 22 22).
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.
- 2d ago First seen · 47 lines · 21 tokens per session scan A c1db73e686fd
gdpr-review is a command published in the GitHub repository fmflurry/settings-opencode (171 stars, last pushed 20d ago), licensed MIT. It adds 21 tokens to every session and 506 once invoked, about $0.0001 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.