Agent skill

Supplementary Measures

by mukul975 in mukul975/Privacy-Data-Protection-Skills

Guides implementation of technical, contractual, and organisational supplementary measures for international data transfers per EDPB Recommendations 01/2020.

Apache-2.0Auto-check passedLegal & Compliance

Install Supplementary Measures

skills CLI
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill supplementary-measures -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mukul975/Privacy-Data-Protection-Skills supplementary-measures --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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/supplementary-measures .claude/skills/supplementary-measures && rm -rf skills-src

Use ~/.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/

Facts

Skill name
supplementary-measures
GitHub stars
301
Token cost
~3.8k tokens
SKILL.md length
1,875 words
Files
5 (incl. scripts, references, assets)
Skills in repo
280
Repo updated
First seen
Licence
Apache-2.0

At a glance

Guides implementation of technical, contractual, and organisational supplementary measures for international data transfers per EDPB Recommendations 01/2020.

  • Works in 8 steps: Identify the specific EEG gaps from the… → For each gap, identify which… → Prioritise technical measures as the… → …
  • Tasks that involve Cryptography
  • SKILL.md covers Overview, Technical Supplementary Measures, Contractual Supplementary… and Organisational Supplementary…, plus 2 more sections
  • Runs Python scripts from its folder

What it does

Supplementary Measures is an agent skill from mukul975/Privacy-Data-Protection-Skills. Guides implementation of technical, contractual, and organisational supplementary measures for international data transfers per EDPB Recommendations 01/2020. Covers encryption, pseudonymisation, split processing, audit rights, transparency obligations, and internal policies. Keywords: supplementary measures, encryption, pseudonymisation, EDPB recommendations, transfer safeguards.

Its SKILL.md is about 3.8k 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 Cryptography and 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.

When your agent uses it

  • Tasks that involve Cryptography
  • Tasks that involve Privacy and GDPR

Example prompts

  • “Use the supplementary-measures skill to guide implementation of technical, contractual, and organisational supplementary measures for international…”
  • “/supplementary-measures”

Requirements

  • Python 3

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Identify the specific EEG gaps from the TIA (Step 3 output).
  2. For each gap, identify which supplementary measure category addresses it.
  3. Prioritise technical measures as the first line of defence — they provide the strongest protection.
  4. Layer contractual measures to create legal obligations that reinforce technical protections.
  5. Add organisational measures to provide governance and verification.
  6. Assess whether the combined package of measures effectively bridges all identified gaps.
  7. If gaps remain unbridgeable, the transfer must not proceed.
  8. Document the selection rationale in the TIA record.

What it can do on your machine

Read from SKILL.md and the folder at commit 9b2ef9e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    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.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Supplementary Measures loads about 3.8k tokens when it runs, and up to ~6.8k if it reads all its reference files. Until then it costs about 101 tokens; SKILL.md has 1,875 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~101
When it runs · the whole SKILL.md, loaded when a task matches
~3.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.8k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from mukul975/Privacy-Data-Protection-Skills at commit 9b2ef9e, republished under its Apache-2.0 licence (© mukul975). 1,875 words, ~3,792 tokens.

Download SKILL.mdSave it as .claude/skills/supplementary-measures/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
supplementary-measures
description
Guides implementation of technical, contractual, and organisational supplementary measures for international data transfers per EDPB Recommendations 01/2020. Covers encryption, pseudonymisation, split processing, audit rights, transparency obligations, and internal policies. Keywords: supplementary measures, encryption, pseudonymisation, EDPB recommendations, transfer safeguards.
license
Apache-2.0
metadata.author
mukul975
metadata.version
1.0
metadata.domain
privacy
metadata.subdomain
cross-border-transfers
metadata.tags
supplementary-measures, encryption, pseudonymisation, edpb-recommendations, transfer-safeguards

Implementing Supplementary Measures

Overview

EDPB Recommendations 01/2020 (Version 2.0, adopted 18 June 2021) establish that where a Transfer Impact Assessment reveals protection gaps in the destination country's legal framework, supplementary measures must be adopted to bring the level of protection up to the EU standard of essential equivalence. These measures fall into three categories: technical, contractual, and organisational. The measures must be effective in practice — not merely theoretical — and their effectiveness must be reassessed at appropriate intervals.

Technical Supplementary Measures

Measure T1: End-to-End Encryption with EU-Held Keys

Description: Personal data is encrypted before leaving the EU/EEA using strong encryption algorithms, with decryption keys held exclusively by the data exporter or a trusted entity within the EU/EEA. The data importer in the third country receives and stores only ciphertext.

Technical specification at Athena Global Logistics:

  • Algorithm: AES-256-GCM for data at rest; ChaCha20-Poly1305 as alternative for streaming data
  • Key management: AWS KMS with Customer Managed Keys (CMK) hosted in the eu-central-1 (Frankfurt) region; keys never exported outside EEA
  • Key rotation: Automatic rotation every 365 days; immediate rotation upon suspected compromise
  • Certificate management: X.509 certificates issued by the internal PKI hosted in Berlin; certificate pinning for API endpoints
  • Implementation: Application-layer encryption performed by the exporter's middleware before data is transmitted to the importer

Effectiveness: High — the third-country government cannot compel the importer to produce plaintext data because the importer does not possess the decryption keys. This measure is effective against compelled disclosure at rest and in transit.

Limitation: Only applicable where the importer does not need to process the data in plaintext. If the importer must read, analyse, or transform the data, this measure alone is insufficient.

Applicable scenario: Backup storage, archival, and transit-only scenarios where the importer serves as a conduit or storage provider.

Measure T2: Pseudonymisation with EU-Held Mapping Table

Description: Directly identifying personal data elements are replaced with pseudonymous identifiers before transfer. The mapping table linking pseudonyms to real identities is held exclusively by the data exporter within the EU/EEA.

Technical specification at Athena Global Logistics:

  • Pseudonymisation method: HMAC-SHA256 with a secret key held in the Berlin key vault; applied to: customer names, email addresses, phone numbers, and customs identification numbers
  • Mapping table: Stored in a dedicated PostgreSQL instance in the Frankfurt data centre; access restricted to the data protection team (4 authorised users)
  • Transfer payload: Pseudonymised dataset retains consignment references, shipping addresses (generalised to city level), and delivery dates — sufficient for the importer to perform logistics operations
  • Re-identification: Only possible by the exporter using the secret HMAC key and mapping table

Effectiveness: High — the transferred dataset cannot be attributed to identified natural persons by the importer or any third party (including government authorities) without access to the mapping table.

Limitation: Requires that the importer can fulfil its processing purpose without accessing the original identifying data. Not suitable where the importer must contact data subjects directly or produce documentation bearing real names.

Measure T3: Split Processing

Description: The processing operation is divided such that no single entity in the third country holds the complete dataset. Each fragment, viewed in isolation, does not constitute personal data or cannot be attributed to an identified individual.

Technical specification at Athena Global Logistics:

  • Architecture: Two-party split where customer identity data (names, contact details) remains in the Frankfurt data centre and only operational data (consignment IDs, routing codes, timestamps) is transferred to the Hong Kong processing centre
  • Linkage prevention: The transferred dataset uses internal reference codes that are meaningful only when joined with the identity dataset held in Frankfurt
  • Recombination: Performed only within the EU/EEA environment by the exporter's analytics platform

Effectiveness: High — neither the importer nor the destination country government can reconstruct the full personal dataset from the transferred fragment alone.

Limitation: Requires significant architectural investment and may reduce the importer's processing efficiency. Applicable only where the processing can be meaningfully divided.

Measure T4: Transport-Layer Encryption

Description: All data transfers are protected by transport-layer security (TLS 1.3 or equivalent) to prevent interception in transit.

Technical specification at Athena Global Logistics:

  • Protocol: TLS 1.3 mandatory for all API endpoints; SFTP with AES-256 for batch file transfers
  • Cipher suites: TLS_AES_256_GCM_SHA384, TLS_CHACHA20_POLY1305_SHA256 (weak cipher suites disabled)
  • Certificate validation: Mutual TLS (mTLS) authentication between exporter and importer systems
  • HSTS: HTTP Strict Transport Security with max-age=31536000, includeSubDomains

Effectiveness: Medium — protects data against interception in transit by third parties but does not protect against compelled disclosure of data at rest by the importer or government authorities accessing the importer's systems.

Applicable as: Baseline measure for all transfers, combined with other measures for comprehensive protection.

Measure T5: Anonymisation Before Transfer

Description: Personal data is irreversibly anonymised before transfer, rendering the transferred dataset outside the scope of the GDPR (Recital 26).

Technical specification at Athena Global Logistics:

  • Technique: k-anonymity (k=5) combined with l-diversity applied to aggregated shipment analytics data
  • Generalisation: Geographic data generalised to country level; dates generalised to month; volumes aggregated to weekly totals
  • Singling-out test: Conducted per WP29 Opinion 05/2014 on Anonymisation Techniques to verify no individual can be singled out, linked, or inferred from the anonymised dataset

Effectiveness: Complete — anonymised data is not personal data and Chapter V transfer rules do not apply. However, the utility of the data for the importer may be significantly reduced.

Contractual Supplementary Measures

Measure C1: Obligation to Challenge Government Access Requests

Contractual clause: The data importer undertakes to challenge any government access request that: (a) is disproportionate to the stated legal objective; (b) exceeds the scope authorised by the applicable legislation; (c) is incompatible with the protections afforded by the SCCs. The importer shall exhaust all available legal remedies before disclosing any data in response to a government request.

Implementation at Athena Global Logistics: Included as Clause 3.1 of the SCC Supplementary Measures Addendum executed with TransPacific Freight Solutions Ltd on 15 March 2025.

Measure C2: Transparency Obligation for Government Access

Contractual clause: The data importer shall notify the data exporter within 48 hours of receiving any government access request relating to transferred personal data. Where local law prohibits notification, the importer shall use best efforts to obtain a waiver of the prohibition and shall, at minimum, provide aggregated statistical information about government requests received on an annual basis.

Implementation: Included as Clause 3.2 of the SCC Supplementary Measures Addendum. Additionally, TransPacific Freight Solutions publishes an annual transparency report covering all government data access requests by jurisdiction and legal basis.

Measure C3: Audit Rights

Contractual clause: The data exporter or its designated independent auditor has the right to conduct on-site or remote audits of the data importer's data processing facilities, systems, and records at least once during each 12-month period, with 30 days' prior written notice. The importer shall cooperate fully with the audit and provide access to all relevant personnel, systems, and documentation.

Implementation: Included in SCC Clause 8.9 and supplemented by Clause 3.3 of the Addendum specifying the audit scope, methodology, and reporting requirements.

Show full SKILL.md (732 more words)Show less
Measure C4: Warrant Canary

Contractual clause: The data importer shall publish a monthly statement confirming that, during the preceding month, it has not received any government order that would require the disclosure of transferred personal data under circumstances that would prevent notification to the data exporter. The absence of such a statement shall serve as notice to the exporter.

Implementation: TransPacific Freight Solutions publishes the warrant canary statement on the 5th business day of each month on a dedicated page of its corporate website accessible to Athena Global Logistics.

Measure C5: Data Localisation Commitment

Contractual clause: The data importer shall not transfer, store, or process the transferred personal data in any jurisdiction other than the agreed destination country (Hong Kong SAR) without the prior written consent of the data exporter. Sub-processor processing in other jurisdictions requires execution of separate SCCs or equivalent safeguards.

Implementation: Included as Clause 3.5 of the Addendum; enforced through technical controls restricting data replication to the Hong Kong data centre only.

Organisational Supplementary Measures

Measure O1: Internal Access Policies

Description: The data importer implements strict role-based access controls limiting data access to the minimum number of named personnel with a documented business need.

Implementation at TransPacific Freight Solutions:

  • 12 named employees authorised to access transferred personal data
  • Access justified by individual role description and approved by the Privacy Officer
  • Quarterly access reviews conducted; access revoked within 24 hours upon role change
  • Access logs retained for 24 months and available to the exporter upon request
Measure O2: Transparency Reports

Description: The data importer publishes periodic transparency reports detailing the number and nature of government data access requests received, to the extent permitted by local law.

Implementation: Annual transparency report published in Q1 covering the preceding calendar year. Report includes: number of requests by jurisdiction, legal basis cited, data categories requested, and outcome (full disclosure, partial disclosure, challenge, withdrawal).

Measure O3: ISO 27001/27701 Certification

Description: The data importer obtains and maintains independent certification against ISO 27001:2022 (information security) and ISO 27701:2019 (privacy information management), providing third-party verification that technical and organisational measures meet international standards.

Implementation: TransPacific Freight Solutions certified to ISO 27001:2022 (certificate valid to 31 December 2026) and ISO 27701:2019 (certificate valid to 31 December 2026). Surveillance audits conducted annually by TUV Rheinland.

Measure O4: Incident Escalation Protocol

Description: Documented procedure for the importer to escalate data protection incidents, including government access events, to the exporter within defined timeframes.

Implementation:

  • Government access request received: Notify exporter within 48 hours (or immediately if disclosure is imminent)
  • Data breach involving transferred data: Notify exporter within 24 hours per SCC Clause 8.6
  • Employee misconduct involving data access: Notify exporter within 72 hours
  • Escalation chain: Importer Privacy Officer → Exporter DPO → Exporter Legal Counsel → Exporter Board (if material)

Effectiveness Assessment Matrix

MeasureTechnical Risk AddressedEffectiveness Against Compelled DisclosureEffectiveness Against Bulk SurveillanceResidual Risk
T1 — E2E encryption with EU keysData at rest and in transitHighHighNone if keys remain in EU
T2 — PseudonymisationRe-identificationHighHighLow — sophisticated attacks may enable re-identification through auxiliary data
T3 — Split processingComplete dataset exposureHighHighLow — requires careful architecture to prevent fragment recombination
T4 — TLS 1.3Transit interceptionHigh (transit only)MediumMedium — does not protect at rest
T5 — AnonymisationAll — data is no longer personalCompleteCompleteNone — but utility is reduced
C1 — Challenge obligationDisproportionate requestsMediumLowMedium — effectiveness depends on importer's legal standing and judiciary
C2 — TransparencyVisibilityMediumLowMedium — may be blocked by gag orders
C3 — Audit rightsCompliance verificationMediumLowMedium — retrospective, not preventive
C4 — Warrant canaryGag order detectionLow-MediumLowHigh — indirect signal only
O1 — Access policiesInsider riskMediumLowMedium — does not prevent compelled disclosure
O2 — Transparency reportsAccountabilityMediumLowMedium — aggregate data only
O3 — ISO certificationControl assuranceMediumLowMedium — certification is point-in-time

Selection Methodology

  1. Identify the specific EEG gaps from the TIA (Step 3 output).
  2. For each gap, identify which supplementary measure category addresses it.
  3. Prioritise technical measures as the first line of defence — they provide the strongest protection.
  4. Layer contractual measures to create legal obligations that reinforce technical protections.
  5. Add organisational measures to provide governance and verification.
  6. Assess whether the combined package of measures effectively bridges all identified gaps.
  7. If gaps remain unbridgeable, the transfer must not proceed.
  8. Document the selection rationale in the TIA record.

© 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

Files

SKILL.md and 4 other files (scripts, references, assets) in skills/privacy/supplementary-measures of mukul975/Privacy-Data-Protection-Skills.

  • SKILL.md
  • assets/template.md
  • references/standards.md
  • references/workflows.md
  • scripts/process.py

Open the folder on GitHubat commit 9b2ef9e

Compare with similar skills

Supplementary Measures 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.

Supplementary Measures compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Supplementary Measures this skillmukul975/Privacy-Data-Protection-Skills301—~3.8kAutomated safety check: PassApache-2.0
Data Protection And Encryptioncbrock84/headcount2k—~1.3kAutomated safety check: PassMIT
Security Compliancesangrokjung/claude-forge8522 repos~7.2kAutomated safety check: PassMIT
Incident Reporting Navigatordavila7/claude-code-templates33k1 repos~4.7kAutomated safety check: PassCC-BY-4.0
Implementing Hashicorp Vault Dynamic Secretsmukul975/Anthropic-Cybersecurity-Skills34k—~5.2kAutomated safety check: PassApache-2.0
Performing Ssl Tls Inspection Configurationmukul975/Anthropic-Cybersecurity-Skills34k—~2.9kAutomated safety check: NotesApache-2.0

Similar skills

  • Protects data itself rather than the systems around it — classifying what you hold, encrypting in transit and at rest and understanding what each actually defends against, managing keys and their…

    2k GitHub stars~1.3k tokensUpdated 22 days ago
    Legal & ComplianceAuto-check passed
  • Security Compliance

    sangrokjung/claude-forge

    Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and…

    852 GitHub starsUsed in 2 repos~7.2k tokens
    Legal & ComplianceAuto-check passed
  • Incident Reporting Navigator

    davila7/claude-code-templates

    A skill your agent uses when a security incident, data breach, or actively exploited vulnerability raises the question "who must we notify, where, and by when?" Screens one incident across the EU…

    33k GitHub starsUsed in 1 repo~4.7k tokens
    Legal & ComplianceAuto-check passed
  • Implementing Hashicorp Vault Dynamic Secrets

    mukul975/Anthropic-Cybersecurity-Skills

    Configures HashiCorp Vault dynamic secrets engines for database credentials, AWS IAM keys, and PKI certificates, with automatic generation, lease management, and rotation to eliminate static secrets…

    34k GitHub stars~5.2k tokensUpdated 1 mo ago
    Legal & ComplianceAuto-check passed
  • Performing Ssl Tls Inspection Configuration

    mukul975/Anthropic-Cybersecurity-Skills

    Configure SSL/TLS break-and-inspect on next-generation firewalls and forward proxies to decrypt, inspect, and re-encrypt HTTPS traffic for malware and exfiltration detection, including deploying…

    34k GitHub stars~2.9k tokensUpdated 1 mo ago
    SecurityAuto-check: notes
  • Agent Decision Receipts

    alirezarezvani/claude-skills

    Mint a tamper-evident, post-quantum-signed receipt for a consequential agent action (deploy, delete, pay, grant-access, model decision) so it can be verified later from the certificate alone.

    28k GitHub stars~2k tokensUpdated 1 mo ago
    Legal & ComplianceAuto-check passed

More from mukul975/Privacy-Data-Protection-Skills

All 280 skills in this repo
  • Age Gating Services

    mukul975/Privacy-Data-Protection-Skills

    Implements age-gating mechanisms for online services to restrict access based on user age.

    301 GitHub stars~3.7k tokensUpdated 6 mo ago
    Auto-check passed
  • AI Data Retention

    mukul975/Privacy-Data-Protection-Skills

    Manages AI model retention and machine unlearning requirements.

    301 GitHub stars~1.9k tokensUpdated 6 mo ago
    Auto-check passed
  • AI Dpia

    mukul975/Privacy-Data-Protection-Skills

    Conducts Data Protection Impact Assessments for AI and ML systems per EDPB Guidelines 04/2025 on AI processing.

    301 GitHub stars~3.4k tokensUpdated 6 mo ago
    Auto-check passed
  • Dpia Mitigation Plan

    mukul975/Privacy-Data-Protection-Skills

    Structures risk mitigation planning and residual risk tracking for Data Protection Impact Assessments under GDPR Article 35(7)(d).

    301 GitHub stars~846 tokensUpdated 6 mo ago
    Auto-check passed
  • Gdpr Accountability

    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.

    301 GitHub stars~1.9k tokensUpdated 6 mo ago
    Auto-check passed
  • Pia Threshold Screening

    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.

    301 GitHub stars~880 tokensUpdated 6 mo ago
    Auto-check passed

Questions about Supplementary Measures

What does Supplementary Measures do?

Guides implementation of technical, contractual, and organisational supplementary measures for international data transfers per EDPB Recommendations 01/2020. Supplementary Measures is an agent skill from mukul975/Privacy-Data-Protection-Skills. Guides implementation of technical, contractual, and organisational supplementary measures for international data transfers per EDPB Recommendations 01/2020.

When should I use Supplementary Measures?

Supplementary Measures fits situations like: tasks that involve Cryptography; tasks that involve Privacy and GDPR.

How do I install Supplementary Measures in Claude Code?

Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill supplementary-measures -a claude-code`. Or copy the skill folder (skills/privacy/supplementary-measures in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/supplementary-measures in your project. Claude Code loads it when a task matches its description.

How do I install Supplementary Measures in Codex?

Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill supplementary-measures -a codex`. Or copy the skill folder (skills/privacy/supplementary-measures in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/supplementary-measures in your project. Codex loads it when a task matches its description.

Can I use Supplementary Measures in Cursor, Gemini CLI or GitHub Copilot?

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 supplementary-measures -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/supplementary-measures, .gemini/skills/supplementary-measures, .github/skills/supplementary-measures and .opencode/skills/supplementary-measures in your project.

What does Supplementary Measures need to run?

Going by SKILL.md and its folder, Supplementary Measures needs Python for the scripts in its folder. Our summary lists: Python 3.

Does Supplementary Measures access the network?

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.

Is Supplementary Measures safe to install?

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.

What licence does Supplementary Measures use?

Supplementary Measures 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.

How many tokens does Supplementary Measures use?

About 3.8k tokens (SKILL.md is roughly 15k 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 3k tokens, read only when the agent opens those files.

What are the alternatives to Supplementary Measures?

Skills that share tags, products or a category with Supplementary Measures: Data Protection And Encryption (cbrock84/headcount, 2k stars), Security Compliance (sangrokjung/claude-forge, 852 stars), Incident Reporting Navigator (davila7/claude-code-templates, 33k stars) and Implementing Hashicorp Vault Dynamic Secrets (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Supplementary Measures?

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.