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 JustineDevs/premortem --skill privacy-policygit clone --depth 1 https://github.com/JustineDevs/premortemWrote 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/justinedevs/premortem/privacy-policy)<a href="https://agentmods.dev/skills/justinedevs/premortem/privacy-policy"><img src="https://agentmods.dev/badge/skills/justinedevs/premortem/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/justinedevs/premortem/privacy-policy"><img src="https://agentmods.dev/badge/skills/justinedevs/premortem/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.00042 | $0.02307 |
| Opus 5 | $0.00021 | $0.01154 |
| Sonnet 5 | $0.00008 | $0.00461 |
| Haiku 4.5 | $0.00004 | $0.00231 |
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 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.
This is a copy
100% identical to privacy-policy — 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Privacy Policy Generator
You are an experienced data privacy and compliance specialist. Your role is to help draft comprehensive, clear, and compliant privacy policies for digital products and services.
Purpose
Draft a detailed privacy policy for a product or service. The policy covers data types handled, applicable jurisdiction, and clearly marks clauses that require legal review. Provide plain-language explanations to ensure accessibility and transparency.
Important Disclaimer
This is for informational purposes only and does not constitute legal advice. Always have a qualified attorney specializing in data privacy law review the final policy before publication. Privacy policies are legally binding documents that establish your company's responsibilities and users' rights; professional legal review is essential.
Input Arguments
$PRODUCT_NAME: Name of the product or service$PRODUCT_URL: URL or description of the product (optional; will be researched if provided)$COMPANY_NAME: Legal name of your company$COMPANY_ADDRESS: Company headquarters or registered address$CONTACT_EMAIL: Email for privacy inquiries (e.g., [email protected])$INFORMATION_TYPES: Types of data collected (e.g., "names, emails, usage behavior, location data, payment information, device identifiers")$JURISDICTION: Applicable jurisdiction (e.g., "United States," "European Union (GDPR)," "California (CCPA)")
Process
Step 1: Research (if URL provided)
If $PRODUCT_URL is provided:
- Visit the product website
- Identify what data is collected (forms, tracking, login, payments)
- Note any third-party integrations (analytics, payment processors, SDKs)
- Understand the product's primary features and use cases
Step 2: Clarify Data Collection
Map out all data your product collects:
- Direct collection: What users enter (name, email, preferences)
- Automatic collection: What is tracked (IP address, usage behavior, device info, cookies)
- Third-party data: What comes from partners, integrations, or service providers
- Special categories: Does the product handle health data, financial data, children's data, biometric data?
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 · 239 lines · 42 tokens per session scan A 4388e746dbde
privacy-policy is a skill published in the GitHub repository JustineDevs/premortem (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 42 tokens to every session and 2,307 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to privacy-policy, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
fda-database
Query openFDA API for drugs, devices, adverse events, recalls, regulatory submissions (510k, PMA), substance identification (UNII), for FDA regulatory data analysis and safety research.
azure-compliance
Run Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration…
legal-drafting
A guide for drafting common legal documents used in mainland China, including court filings, lawyer letters, legal opinions, and contract drafts. It marks facts, amounts, legal grounds, and other details that still need verification.
legal-compliance
A China-mainland compliance review guide for products, business activities, and marketing claims. It checks areas such as the Personal Information Protection Law (PIPL), data security, intellectual property, third parties, industry rules, and AI governance.
legal-reasoning
A legal-analysis aid that organizes a case into issue, rule, application, and conclusion, a method often called IRAC. It separates rules that have been verified from general legal ideas that still need checking.
open-weights
Use when choosing an open-weight LLM and clearing it for use — which family and size fit the task, the hardware and the budget, and above all whether the license permits shipping. Owns the license-class map (OSI-open versus custom-community versus non-commercial), the always-verify-the-model-card rule, size-to-VRAM…