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 ljucask/pureinn-product-development --skill pm-privacy-requirementsgit clone --depth 1 https://github.com/ljucask/pureinn-product-developmentWrote 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/ljucask/pureinn-product-development/pm-privacy-requirements)<a href="https://agentmods.dev/skills/ljucask/pureinn-product-development/pm-privacy-requirements"><img src="https://agentmods.dev/badge/skills/ljucask/pureinn-product-development/pm-privacy-requirements/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/ljucask/pureinn-product-development/pm-privacy-requirements"><img src="https://agentmods.dev/badge/skills/ljucask/pureinn-product-development/pm-privacy-requirements.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.00052 | $0.04768 |
| Opus 5 | $0.00026 | $0.02384 |
| Sonnet 5 | $0.00010 | $0.00954 |
| Haiku 4.5 | $0.00005 | $0.00477 |
Grade A, and why
pm-privacy-requirements 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 12d 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 — 474 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM - Privacy Requirements
Agent mode (--agent)
Supports --agent: runs autonomously in a subagent, drafts the artifact from existing inputs, and returns a short summary + coverage note.
- No flag → interactive (default); if inputs are heavy, offer agent mode.
--agent→ obey. First check inputs are complete. Anything missing: do NOT invent it - mark[ASSUMED - what/why]in the output and summary. Never hallucinate to fill a gap.
What this skill does
Maps the domain model to privacy and data protection obligations. Produces:
- PII Inventory - which entities contain personal data, what type, and how sensitive
- Privacy Requirements - what the system must do to comply (consent, retention, rights)
- GDPR Action Plan - concrete actions with owners and timing before launch
This skill runs after pm-domain-model - entities must be defined to inventory PII accurately. Output feeds directly into Phase 6 (pm-feature-design references privacy rules in Feature Card Section 1 for features that handle personal data).
This is a PM-level analysis, not a legal opinion. Validate with legal counsel before launch.
Dependencies
Required before running:
pm-domain-model- entities and their attributes are the input for PII mapping
Recommended before running:
pm-domain-analysis- legal requirements from Phase 2 provide the regulatory baseline
Produces artifacts used by:
pm-business-rules-library- privacy rules become RULE-A and RULE-C entries inbusiness_rules.mdpm-feature-design- consent flows, data export, deletion - specified JIT in Feature Card Section 1- Phase 6 build - developers need privacy requirements before implementing user-facing features
Step 0: Current state check
Check for existing artifacts:
- PII Inventory
- Privacy Requirements
- GDPR Action Plan
Also check: does a Domain Model exist? Without it, the PII inventory will be incomplete - flag this. Does a Legal & Regulatory Requirements document exist from Phase 2? Cross-reference regulatory scope stated there.
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.
- 12d ago First seen · 474 lines · 52 tokens per session scan A 00514c905ca3
pm-privacy-requirements is a skill published in the GitHub repository ljucask/pureinn-product-development (2 stars, last pushed 2d ago), licensed MIT. It adds 52 tokens to every session and 4,768 once invoked, about $0.0003 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 skills, from other repositories
akf-trust-metadata
The AI native file format. EXIF for AI — stamps every file with trust scores, source provenance, and compliance metadata. Embeds into 20+ formats (DOCX, PDF, images, code). EU AI Act, SOX, HIPAA auditing.
c2pa-metadata
Embed a C2PA provenance manifest into an AI-generated marketing asset (PNG, JPG, WebP, GIF, TIFF, MP4, MOV, WebM, MP3, WAV, PDF) via scripts/embed-c2pa.py — produces a signed copy of the file carrying IPTC digital-source-type AI claims, an optional c2pa.ai-disclosure assertion for EU AI Act Article 50 (applicable 2…
chief-legal-and-risk-officer
Owns legal, contracts, intellectual property, regulatory compliance, privacy, security governance, enterprise risk, and audit readiness. Use this to review a contract or commitment, assess regulatory or privacy exposure, evaluate an IP or licensing question, judge the risk in a business decision, prepare for an audit…
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…
intellectual-property
Covers what the organization owns and what it is only borrowing — trademarks and clearance, copyright and work-for-hire, patents and trade secrets, open-source license obligations and copyleft reach, and IP terms in customer, contractor and AI-tool agreements. Use this to check whether a name is usable, establish that…
employment-compliance
Covers the employment rules that carry real penalties — exempt and non-exempt classification, overtime and hours, employee versus contractor status, work authorization and recordkeeping, accommodation requests, and the notices and retention obligations that go with them. Use this to classify a role, review a…