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/Dokkabei97/forged-claude-codeWrote 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/dokkabei97/forged-claude-code/privacy-policy-generator)<a href="https://agentmods.dev/commands/dokkabei97/forged-claude-code/privacy-policy-generator"><img src="https://agentmods.dev/badge/commands/dokkabei97/forged-claude-code/privacy-policy-generator.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.00020 | $0.01157 |
| Opus 5 | $0.00010 | $0.00579 |
| Sonnet 5 | $0.00004 | $0.00231 |
| Haiku 4.5 | $0.00002 | $0.00116 |
Grade A, and why
privacy-policy-generator 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/privacy-policy-generator - Privacy & Terms Generator
Triggers
- When preparing for product launch and need legal documents
- When adding new data collection features
- When expanding to new markets (EU, Korea, US)
Usage
/privacy-policy-generator [product name]
/privacy-policy-generator --type privacy # Privacy policy only
/privacy-policy-generator --type terms # Terms of service only
/privacy-policy-generator --type both # Both documents
/privacy-policy-generator --locale kr # Korean law focus
/privacy-policy-generator --locale eu # GDPR focus
/privacy-policy-generator --locale us # US/CCPA focus
Behavioral Flow
Phase 1: Data Collection Audit
Gather information about data practices:
1. What personal data do you collect?
- Account: email, name, password
- Payment: card info, billing address
- Usage: analytics, logs, cookies
- Third-party: social login data
2. How is data used?
- Service delivery
- Analytics and improvement
- Marketing communications
- Third-party sharing
3. Where is data stored?
- Cloud provider and region
- Third-party services (Stripe, analytics, etc.)
4. What is the retention period?
- Active account data
- Deleted account data
- Log data
Phase 2: Generate Documents
Privacy Policy Structure:
# Privacy Policy — [Product Name]
**Effective Date**: [Date]
**Last Updated**: [Date]
## 1. Information We Collect
### Information You Provide
[Account info, payment info, content you create]
### Information Collected Automatically
[Device info, usage data, cookies, analytics]
### Information from Third Parties
[Social login, payment processors]
## 2. How We Use Your Information
[Service delivery, improvement, communication, legal compliance]
## 3. How We Share Your Information
[Service providers, legal requirements, business transfers]
[We do NOT sell personal information]
## 4. Data Retention
[How long we keep data and why]
## 5. Your Rights
### For Korean Users (개인정보보호법)
- 개인정보 열람, 정정, 삭제, 처리정지 요구권
- 개인정보 처리에 대한 동의 철회권
### For EU Users (GDPR)
- Right to access, rectification, erasure
- Right to data portability
- Right to object to processing
- Right to withdraw consent
## 6. Data Security
[Encryption, access controls, security measures]
## 7. Children's Privacy
[Age restrictions, parental consent if applicable]
## 8. International Data Transfers
[Cross-border data transfer mechanisms]
## 9. Cookies
[Types of cookies used, how to manage them]
## 10. Changes to This Policy
[How users will be notified of changes]
## 11. Contact Us
[Data protection officer or contact info]
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 · 188 lines · 20 tokens per session scan A 1adedfbf7eda
privacy-policy-generator is a command published in the GitHub repository Dokkabei97/forged-claude-code (2 stars, last pushed 6mo ago), licensed MIT. It adds 20 tokens to every session and 1,157 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-31.
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.
scope
Mandatory pre-flight scope check — verify an asset is in scope BEFORE any HTTP touch. Deterministic (deny-wins, default-deny) via engine/scope.py against the engagement's scope.md. Blocks out-of-scope testing. Usage: /scope [ ...].
p0-regulatory
Identifies regulatory requirements, DSGVO (GDPR) obligations, and legal knock-out criteria early on, before significant time is invested in the idea. A regulatory showstopper should be recognised as early as possible.
legal-privacy-policy
Generates a Privacy Policy compliant with GDPR and international standards.
gate-p7-business
Checks business readiness: documentation, GTM, KPIs, legal mandatory documents.
mindforge:fintech
Design fintech payment/ledger architecture. Usage: /mindforge:fintech [service] [--domain payments|ledger|kyc] [--compliance pci|sox].