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 mukul975/Privacy-Data-Protection-Skills --skill consent-record-keepinggit clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-SkillsWrote 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/mukul975/privacy-data-protection-skills/consent-record-keeping)<a href="https://agentmods.dev/skills/mukul975/privacy-data-protection-skills/consent-record-keeping"><img src="https://agentmods.dev/badge/skills/mukul975/privacy-data-protection-skills/consent-record-keeping/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/mukul975/privacy-data-protection-skills/consent-record-keeping"><img src="https://agentmods.dev/badge/skills/mukul975/privacy-data-protection-skills/consent-record-keeping.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.00060 | $0.02099 |
| Opus 5 | $0.00030 | $0.01050 |
| Sonnet 5 | $0.00012 | $0.00420 |
| Haiku 4.5 | $0.00006 | $0.00210 |
Grade A, and why
consent-record-keeping 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Building Consent Record-Keeping
Overview
GDPR Article 7(1) states: "Where processing is based on consent, the controller shall be able to demonstrate that the data subject has consented to the processing of personal data." This obligation to demonstrate consent requires comprehensive record-keeping that captures not only the consent decision but the context in which it was made.
The Kantara Initiative Consent Receipt Specification (v1.1) provides a standardized machine-readable format for consent receipts that satisfies regulatory expectations and enables interoperability.
Required Record Fields
Per EDPB Guidelines 05/2020 (paragraphs 89-107), demonstrating consent requires preserving evidence of:
Core Fields (Mandatory)
| Field | Description | GDPR Reference | Format |
|---|---|---|---|
| consent_id | Unique identifier for this consent decision | Art. 7(1) | UUID v4 |
| subject_id | Identifier of the data subject | Art. 7(1) | UUID v4 |
| purpose_id | Identifier of the processing purpose | Art. 6(1)(a) | Purpose code |
| purpose_description | Plain-language description of the purpose | Art. 13(1)(c) | Text |
| decision | Consent granted or not granted | Art. 7(1) | Enum: granted, not_granted |
| timestamp | When the decision was made | Art. 7(1) | ISO 8601 UTC |
| mechanism | How consent was expressed | Art. 4(11) | Enum: checkbox_tick, toggle_switch, typed_statement, signature |
| consent_text_version | Hash of the exact consent text shown | Art. 7(1) | SHA-256 hex |
| consent_text | The exact text presented to the data subject | Art. 7(2) | Full text |
| controller_name | Legal name of the data controller | Art. 13(1)(a) | Text |
| controller_contact | Controller contact information | Art. 13(1)(a) | Text |
Contextual Fields (Recommended)
| Field | Description | GDPR Reference | Format |
|---|---|---|---|
| ip_address | IP address at time of consent | Art. 7(1) proof | IPv4/IPv6 |
| user_agent | Browser/device user agent string | Art. 7(1) proof | Text |
| session_id | Session identifier | Art. 7(1) proof | UUID |
| source | Where consent was collected | Art. 7(1) proof | Enum: signup, preference_center, cookie_banner |
| data_categories | Categories of personal data for this purpose | Art. 13(1)(d) | JSON array |
| recipients | Named third-party recipients | Art. 13(1)(e) | JSON array |
| retention_period | How long data is retained for this purpose | Art. 13(2)(a) | Text |
| withdrawal_info | Instructions for withdrawing consent | Art. 7(3) | Text |
| dpo_contact | DPO contact information | Art. 13(1)(b) | Text |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 189 lines · 60 tokens per session scan A f7ca773bc738
consent-record-keeping is a skill published in the GitHub repository mukul975/Privacy-Data-Protection-Skills (272 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 60 tokens to every session and 2,099 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-30.
Other skills, from other repositories
privacy-compliance
Comprehensive global privacy compliance agent skill covering GDPR, CCPA/CPRA, HIPAA Privacy Rule, EU AI Act, LGPD, cross-border data transfer mechanisms (SCCs, BCRs, EU-US DPF), PII identification and classification, data minimization, consent management, privacy-by-design patterns, DPIA workflows, data subject access…
fedramp
Expert guidance for FedRAMP certification and compliance under CR26 (FedRAMP Consolidated Rules for 2026). Use this skill whenever a user asks about FedRAMP authorization, ATO (Authority to Operate), cloud security for federal government, NIST SP 800-53 controls, CSP compliance, or any of the core FedRAMP document…
iso42001
Expert ISO 42001 AI Management System (AIMS) compliance advisor. Use this skill whenever a user asks about ISO/IEC 42001:2023, AI governance, AI management systems, AI risk assessment, AI system impact assessment, Annex A controls for AI, Statement of Applicability for AI systems, AI policy, responsible AI, AI…
eu-cra
Expert EU Cyber Resilience Act (CRA) advisor for Regulation (EU) 2024/2847 — mandatory cybersecurity and vulnerability handling requirements for all products with digital elements (PDEs) sold in the EU. Use this skill for gap analysis, product classification (Default / Class I / Class II), conformity assessment route…
gdpr-compliance
Expert GDPR compliance assistant covering all four core workflows: (1) auditing code and systems for GDPR violations, (2) drafting GDPR-compliant documents such as privacy policies, Data Processing Agreements (DPAs), and consent notices, (3) answering GDPR compliance questions with authoritative article citations, and…
nist-800-53
NIST SP 800-53 Rev 5 compliance advisor — all 20 control families (AC, AT, AU, CA, CM, CP, IA, IR, MA, MP, PE, PL, PM, PS, PT, RA, SA, SC, SI, SR), Low/Moderate/High baseline selection, FIPS 199/200 system categorization, control tailoring and overlays, privacy controls (PT family), supply chain risk management (SR…