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 bromso/metapowers --skill privacy-policygit clone --depth 1 https://github.com/bromso/metapowersWrote 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/bromso/metapowers/privacy-policy)<a href="https://agentmods.dev/skills/bromso/metapowers/privacy-policy"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/privacy-policy/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/skills/bromso/metapowers/privacy-policy"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/privacy-policy.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.00072 | $0.00989 |
| Opus 5.5 | $0.00029 | $0.00396 |
| Sonnet 5.5 | $0.00014 | $0.00198 |
| Haiku 4.5 | $0.00007 | $0.00099 |
Grade A, and why
privacy-policy 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 3d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Privacy Policy
Draft a GDPR/CCPA-compliant privacy policy for "$ARGUMENTS". Generate a comprehensive privacy policy that satisfies major data protection regulations.
Note: AI-generated legal content does not constitute legal advice. Consult a qualified attorney.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .metapowers/legal/<project>/skip-log.md: - <ISO timestamp> — <skill name> skipped prerequisite check for <artifact file> — reason: <reason or "none given">.
Prerequisites
Check that .metapowers/legal/<project>/00-assess.md exists. If it does not exist, stop and tell the user:
"Run an Assess skill first (e.g.
/legal:risk-assessment <project>) to generate the prerequisite assessment artifact."
Process
-
Read inputs:
- Read
.metapowers/legal/<project>/00-assess.mdfor risk, jurisdiction, and data practice context
- Read
-
Identify data practices:
- What personal data is collected (categories and specific examples)
- How data is collected (directly from users, automatically, from third parties)
- Purposes for processing each data category
- Lawful basis for processing under GDPR (consent, contract, legitimate interest, legal obligation, vital interest, public task)
- Data sharing relationships with third parties
- Data retention timelines per category
- International data transfer mechanisms
-
Draft GDPR Article 13/14 compliant sections:
- Data Controller Identity and Contact — legal name, address, contact details, EU representative (if applicable)
- Data Collected — categories with specific examples (identifiers, contact info, financial data, usage data, device data, location data, etc.)
- Purposes and Lawful Basis — per-category breakdown of why data is processed and the legal basis for each
- Data Sharing with Third Parties — who receives data, why, and in what capacity (processor vs. controller)
- Data Retention Periods — per-category retention periods with rationale
- User Rights — access, rectification, erasure, restriction, portability, objection, and how to exercise each right
- Automated Decision-Making and Profiling — whether used, logic involved, significance and consequences, right to opt out
- Cookie Usage — summary with link to full cookie policy
- International Data Transfers — transfer mechanisms (SCCs, adequacy decisions, BCRs) and safeguards
- Children's Privacy — age restrictions, COPPA compliance (if applicable), parental consent mechanisms
- Policy Updates Procedure — how changes are communicated, effective date handling
- DPO / Contact Information — Data Protection Officer details (if appointed), supervisory authority contact, complaint procedures
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.
- 3d ago First seen · 68 lines · 72 tokens per session scan A e96c4548cc3a
privacy-policy is a skill published in the GitHub repository bromso/metapowers (2 stars, last pushed 2d ago), licensed MIT. It adds 72 tokens to every session and 989 once invoked, about $0.0003 per session on Opus 5.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-10-21.
Other skills, from other repositories
chief-human-resources-officer
Owns the organization itself: org design, hiring, performance, compensation, development, culture, and employee relations. Use this to design or restructure a team, plan hiring, write a role or leveling definition, handle a performance or compensation question, diagnose why a team is underperforming for non-technical…
tax
Structures the tax questions a growing business faces — corporate income, sales and use, payroll, nexus, and the obligations created by hiring or selling somewhere new. Use this to work out what a new state or country obligates you to, prepare for a tax filing or audit, understand sales tax on your product, or check…
contract-review
Reviews and negotiates commercial agreements — MSAs, SOWs, order forms, NDAs, vendor and data-processing agreements — identifying material risk, proposing positions, and recommending a path rather than listing issues. Use this to review a contract before signature, prepare a negotiation position, build fallback…
corporate-governance
Maintains the corporate record and the governance machinery — entity records, board and committee support, resolutions and minutes, delegations of authority, insurance, and business continuity. Use this to prepare board or committee materials, record a decision that needs to be minuted, set or check approval…
design-method
Use when starting any design task — resolves register, sets the 3 dials, locks Gate 0, and routes to the right move and target skill.
design-webapp
Use when building or extending a dashboard, SaaS screen, or any authenticated app surface — use design-web instead for a marketing site.