C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Implement the NIST Privacy Framework CONTROL function covering CT.DM data management, CT.DP data processing policies and procedures, and CT.PO disassociated processing.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill nist-pf-control -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills nist-pf-control --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/privacy/nist-pf-control .claude/skills/nist-pf-control && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "nist-pf-control" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/nist-pf-control into .claude/skills/nist-pf-control/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nist-pf-control", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/nist-pf-controlType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill nist-pf-control -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills nist-pf-control --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/privacy/nist-pf-control .agents/skills/nist-pf-control && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "nist-pf-control" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/nist-pf-control into .agents/skills/nist-pf-control/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nist-pf-control", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill nist-pf-control -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills nist-pf-control --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/privacy/nist-pf-control .cursor/skills/nist-pf-control && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "nist-pf-control" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/nist-pf-control into .cursor/skills/nist-pf-control/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nist-pf-control", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mukul975/Privacy-Data-Protection-Skills.git --path skills/privacy/nist-pf-control--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill nist-pf-control -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills nist-pf-control --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/privacy/nist-pf-control .gemini/skills/nist-pf-control && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "nist-pf-control" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/nist-pf-control into .gemini/skills/nist-pf-control/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nist-pf-control", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mukul975/Privacy-Data-Protection-Skills nist-pf-controlInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill nist-pf-control -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/privacy/nist-pf-control .github/skills/nist-pf-control && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "nist-pf-control" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/nist-pf-control into .github/skills/nist-pf-control/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nist-pf-control", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill nist-pf-control -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills nist-pf-control --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/privacy/nist-pf-control .opencode/skills/nist-pf-control && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "nist-pf-control" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/nist-pf-control into .opencode/skills/nist-pf-control/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nist-pf-control", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
nist-pf-controlImplement the NIST Privacy Framework CONTROL function covering CT.DM data management, CT.DP data processing policies and procedures, and CT.PO disassociated processing.
Nist Pf Control is an agent skill from mukul975/Privacy-Data-Protection-Skills. Implement the NIST Privacy Framework CONTROL function covering CT.DM data management, CT.DP data processing policies and procedures, and CT.PO disassociated processing. Provides technical control architectures, data management workflows, and de-identification implementation guidance.
Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts, reference files and assets (for example `assets/template.md`, `references/standards.md` and `references/workflows.md`).
It sits in Legal & Compliance, covering Privacy and GDPR. The repository describes itself as: 282+ structured privacy & data protection skills for AI agents. GDPR, CCPA, EU AI Act, HIPAA, LGPD, PIPL, DPDP Act. The licence is Apache-2.0.
Read from SKILL.md and the folder at commit 9b2ef9e. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 1 file in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Nist Pf Control loads about 2.5k tokens when it runs, and up to ~3.3k if it reads all its reference files. Until then it costs about 75 tokens; SKILL.md has 925 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from mukul975/Privacy-Data-Protection-Skills at commit 9b2ef9e, republished under its Apache-2.0 licence (© mukul975). 925 words, ~2,509 tokens.
.claude/skills/nist-pf-control/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.The CONTROL function develops and implements appropriate activities to enable organizations and individuals to manage data with sufficient granularity to manage privacy risks. It addresses data management, data processing governance, and disassociated processing techniques.
Policies and procedures for managing data throughout its lifecycle.
| Subcategory | Description | Implementation Guidance |
|---|---|---|
| CT.DM-P1 | Data elements can be accessed for review | Implement data subject access portals. Provide export in machine-readable formats (JSON, CSV). Response within regulatory timelines. |
| CT.DM-P2 | Data elements can be accessed for transmission or disclosure | Support data portability requests. Implement secure transfer mechanisms. Maintain disclosure logs. |
| CT.DM-P3 | Data elements can be accessed for alteration | Enable data correction workflows. Propagate corrections across all systems holding the data. |
| CT.DM-P4 | Data elements can be accessed for deletion | Implement cascading deletion across primary and backup systems. Maintain deletion verification logs. Address data in analytics pipelines. |
| CT.DM-P5 | Data processing activities are configured to meet the organization's data processing principles | Default to most privacy-protective settings. Implement purpose limitation at the system level. |
| CT.DM-P6 | Retention schedules are established and in place | Define retention periods per data category. Implement automated purging. Document legal hold exceptions. |
| CT.DM-P7 | Data are processed in accordance with established retention schedules | Automated enforcement of retention policies. Regular audits of data stores. Reporting on retention compliance. |
| CT.DM-P8 | Integrity of data elements is maintained | Implement checksums and validation rules. Detect and resolve data quality issues. Track data lineage. |
| CT.DM-P9 | Audit/log records are determined, documented, implemented, and reviewed | Privacy-specific audit logging for all data access and modifications. Log retention per regulatory requirements. |
| CT.DM-P10 | Mechanisms for data subjects to authorize processing exist | Consent collection and management infrastructure. Granular consent options. Consent withdrawal capability. |
Governance controls for data processing activities.
| Subcategory | Description | Implementation Guidance |
|---|---|---|
| CT.DP-P1 | Policies, processes, and procedures for authorizing data processing are maintained and enforced | Document lawful basis for each processing activity. Implement access controls aligned with authorized purposes. |
| CT.DP-P2 | Data processing environment is identified, managed, and monitored | Maintain environment inventory (production, staging, development). Monitor for unauthorized processing. Separate test data from production data. |
| CT.DP-P3 | Data processing procedures are maintained and monitored to meet established terms | Standard operating procedures for each processing type. Automated compliance checking. Exception management workflow. |
| CT.DP-P4 | System or device configurations are set to authorized specifications | Secure configuration baselines for systems processing personal data. Configuration drift detection. Change management for privacy-relevant settings. |
| CT.DP-P5 | Data processing activities are monitored and logged | Real-time monitoring of data processing operations. Anomaly detection for unusual processing patterns. Alerting for policy violations. |
Techniques to process data while minimizing identifiability.
| Subcategory | Description | Implementation Guidance |
|---|---|---|
| CT.PO-P1 | De-identification is applied to data elements to limit observability or linkability | Apply pseudonymization, anonymization, or generalization based on use case. Document de-identification methodology. |
| CT.PO-P2 | Technical measures for disassociated processing are implemented | Deploy differential privacy, secure multi-party computation, or homomorphic encryption as appropriate. Select technique based on data utility requirements. |
Collection --> Storage --> Processing --> Sharing --> Retention --> Deletion
| | | | | |
v v v v v v
Consent Encryption Purpose Access Schedule Cascading
Capture at Rest Limitation Controls Enforcement Purge
| | | | | |
v v v v v v
Audit Log Access Log Process Log Transfer Log Retention Log Deletion Log| Operation | Data Subject | Data Steward | Processor | Analyst | Admin |
|---|---|---|---|---|---|
| View own data | Yes | Yes | No | No | Yes |
| Export own data | Yes | Yes | No | No | Yes |
| Correct own data | Request | Yes | No | No | Yes |
| Delete own data | Request | Yes | No | No | Yes |
| View aggregate | No | Yes | Yes | Yes | Yes |
| Process data | No | No | Yes | No | Yes |
| Analyze data | No | No | No | Yes | Yes |
| Configure system | No | No | No | No | Yes |
| Technique | Identifiability Reduction | Data Utility | Computational Cost | Reversible |
|---|---|---|---|---|
| Pseudonymization | Medium | High | Low | Yes (with key) |
| k-Anonymity | Medium-High | Medium | Medium | No |
| l-Diversity | High | Medium | Medium | No |
| t-Closeness | High | Medium-Low | High | No |
| Differential Privacy | Very High | Medium | Medium | No |
| Data Masking | Low-Medium | Medium | Low | Depends |
| Generalization | Medium | Medium | Low | No |
| Suppression | High | Low | Low | No |
| Synthetic Data | Very High | Variable | High | No |
Is the data being shared externally?
├── Yes → Is re-identification risk acceptable?
│ ├── No → Apply formal anonymization (differential privacy, k-anonymity with k>=5)
│ └── Yes → Apply pseudonymization with contractual controls
└── No → Is the data used for analytics?
├── Yes → Apply aggregation or differential privacy
└── No → Apply pseudonymization with access controls| Data Category | Retention Period | Legal Basis | Deletion Method | Verification |
|---|---|---|---|---|
| Customer transaction records | 7 years from transaction | Tax/accounting regulations | Secure overwrite | Automated audit |
| Marketing consent records | Duration of consent + 3 years | Legitimate interest (proof) | Logical deletion | Annual review |
| Employee personnel files | Employment + 7 years | Employment law | Secure destruction | HR verification |
| Website analytics | 26 months | Consent | Automated purge | Monthly check |
| Support tickets | 3 years from resolution | Contract performance | Secure overwrite | Quarterly audit |
| CCTV footage | 30 days | Legitimate interest | Automated overwrite | Weekly check |
| Backup tapes | 90 days rolling | Business continuity | Tape degaussing | Quarterly audit |
| Event Category | Specific Events | Required Fields |
|---|---|---|
| Data Access | View, export, download | User ID, timestamp, data subject ID, data elements accessed, purpose |
| Data Modification | Create, update, correct | User ID, timestamp, data subject ID, before/after values, purpose |
| Data Deletion | Delete, purge, anonymize | User ID, timestamp, data subject ID, deletion scope, verification |
| Consent Changes | Grant, withdraw, modify | Data subject ID, timestamp, consent scope, collection channel |
| Data Transfer | Internal transfer, external disclosure | User ID, timestamp, recipient, data elements, legal basis |
| Configuration | Access control changes, retention policy changes | Admin ID, timestamp, before/after settings, approval reference |
| NIST PF CONTROL | ISO 27701 | GDPR Article | NIST 800-53 |
|---|---|---|---|
| CT.DM-P1 | A.7.3.3 | Art. 15 | PM-25 |
| CT.DM-P2 | A.7.3.7 | Art. 20 | PM-25 |
| CT.DM-P3 | A.7.3.4 | Art. 16 | PM-25 |
| CT.DM-P4 | A.7.3.5 | Art. 17 | PM-25 |
| CT.DM-P6 | A.7.4.7 | Art. 5(1)(e) | SI-12 |
| CT.DM-P9 | A.7.2.8 | Art. 30 | AU-2 |
| CT.DM-P10 | A.7.2.3 | Art. 6, 7 | IP-1 |
| CT.DP-P1 | A.7.2.2 | Art. 6(1) | PT-3 |
| CT.DP-P5 | A.7.2.8 | Art. 30 | AU-6 |
| CT.PO-P1 | A.7.4.5 | Art. 25(1) | PM-24 |
| CT.PO-P2 | A.7.4.5 | Art. 25(1) | PM-24 |
© mukul975, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 4 other files (scripts, references, assets) in skills/privacy/nist-pf-control of mukul975/Privacy-Data-Protection-Skills.
Open the folder on GitHubat commit 9b2ef9e
Nist Pf Control next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Nist Pf Control this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~2.5k | Automated safety check: Pass | Apache-2.0 | |
| C15tc15t/c15t | 1.9k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| HIPAA Safe Harbor Coverage Auditmaziyarpanahi/openmed | 5.5k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Korean Privacy Termskimlawtech/korean-privacy-terms | 587 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Gdpr ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~3.9k | Automated safety check: Pass | MIT | |
| Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~2.3k | Automated safety check: Pass | MIT |
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
maziyarpanahi/openmed
Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.
kimlawtech/korean-privacy-terms
처리방침·이용약관 자동 생성 스킬 패키지 (v4.0). An agent skill from kimlawtech/korean-privacy-terms.
Sushegaad/Claude-Skills-Governance-Risk-and-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…
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert HIPAA compliance assistant for healthcare and software contexts.
gregmos/PII-Shield
Universal legal document processor with PII anonymization. An agent skill from gregmos/PII-Shield.
mukul975/Privacy-Data-Protection-Skills
Implements age-gating mechanisms for online services to restrict access based on user age.
mukul975/Privacy-Data-Protection-Skills
Manages AI model retention and machine unlearning requirements.
mukul975/Privacy-Data-Protection-Skills
Conducts Data Protection Impact Assessments for AI and ML systems per EDPB Guidelines 04/2025 on AI processing.
mukul975/Privacy-Data-Protection-Skills
Structures risk mitigation planning and residual risk tracking for Data Protection Impact Assessments under GDPR Article 35(7)(d).
mukul975/Privacy-Data-Protection-Skills
Guides implementation of the GDPR accountability principle under Articles 5(2) and 24, including documentation requirements for policies, DPIAs, RoPA, training records, and breach logs.
mukul975/Privacy-Data-Protection-Skills
Conducts pre-DPIA threshold screening to determine whether a full Data Protection Impact Assessment is required under GDPR Article 35.
Categories
Implement the NIST Privacy Framework CONTROL function covering CT.DM data management, CT.DP data processing policies and procedures, and CT.PO disassociated processing. Nist Pf Control is an agent skill from mukul975/Privacy-Data-Protection-Skills.PO disassociated processing.
Nist Pf Control fits situations like: tasks that involve Privacy and GDPR.
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill nist-pf-control -a claude-code`. Or copy the skill folder (skills/privacy/nist-pf-control in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/nist-pf-control in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill nist-pf-control -a codex`. Or copy the skill folder (skills/privacy/nist-pf-control in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/nist-pf-control in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill nist-pf-control -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nist-pf-control, .gemini/skills/nist-pf-control, .github/skills/nist-pf-control and .opencode/skills/nist-pf-control in your project.
Going by SKILL.md and its folder, Nist Pf Control needs Python for the scripts in its folder. Our summary lists: Python 3.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Nist Pf Control is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 791 tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Nist Pf Control: C15t (c15t/c15t, 1.9k stars), HIPAA Safe Harbor Coverage Audit (maziyarpanahi/openmed, 5.5k stars), Korean Privacy Terms (kimlawtech/korean-privacy-terms, 587 stars) and Gdpr Compliance (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
mukul975 (a GitHub user) maintains it in mukul975/Privacy-Data-Protection-Skills, which has 301 GitHub stars. The repository holds 280 skills in this directory. The repository was last updated on March 16, 2026.
Source: mukul975/Privacy-Data-Protection-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.