C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Implements CPRA Section 1798.135 opt-out preference signal handling, covering Global Privacy Control (GPC) technical detection, automated signal honoring, cross-device consistency, and the…
Install Cpra Opt Out Signals
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill cpra-opt-out-signals -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills cpra-opt-out-signals --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/cpra-opt-out-signals .claude/skills/cpra-opt-out-signals && 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 "cpra-opt-out-signals" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cpra-opt-out-signals into .claude/skills/cpra-opt-out-signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cpra-opt-out-signals", 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/cpra-opt-out-signalsType 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 cpra-opt-out-signals -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills cpra-opt-out-signals --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/cpra-opt-out-signals .agents/skills/cpra-opt-out-signals && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cpra-opt-out-signals" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cpra-opt-out-signals into .agents/skills/cpra-opt-out-signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cpra-opt-out-signals", 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 cpra-opt-out-signals -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills cpra-opt-out-signals --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/cpra-opt-out-signals .cursor/skills/cpra-opt-out-signals && 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 "cpra-opt-out-signals" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cpra-opt-out-signals into .cursor/skills/cpra-opt-out-signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cpra-opt-out-signals", 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/cpra-opt-out-signals--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 cpra-opt-out-signals -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills cpra-opt-out-signals --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/cpra-opt-out-signals .gemini/skills/cpra-opt-out-signals && 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 "cpra-opt-out-signals" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cpra-opt-out-signals into .gemini/skills/cpra-opt-out-signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cpra-opt-out-signals", 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 cpra-opt-out-signalsInstalls 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 cpra-opt-out-signals -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/cpra-opt-out-signals .github/skills/cpra-opt-out-signals && 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 "cpra-opt-out-signals" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cpra-opt-out-signals into .github/skills/cpra-opt-out-signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cpra-opt-out-signals", 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 cpra-opt-out-signals -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 cpra-opt-out-signals --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/cpra-opt-out-signals .opencode/skills/cpra-opt-out-signals && 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 "cpra-opt-out-signals" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/cpra-opt-out-signals into .opencode/skills/cpra-opt-out-signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cpra-opt-out-signals", 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.
Facts
- Skill name
cpra-opt-out-signals- GitHub stars
- 301
- Token cost
- ~2k tokens
- SKILL.md length
- 871 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Implements CPRA Section 1798.135 opt-out preference signal handling, covering Global Privacy Control (GPC) technical detection, automated signal honoring, cross-device consistency, and the…
- Works in 7 steps: Detect the GPC Signal → Map GPC Signal to Consumer → Automated Honoring → …
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, Legal Foundation, Technical Implementation and Monitoring and Testing
- Runs Python scripts from its folder
What it does
Cpra Opt Out Signals is an agent skill from mukul975/Privacy-Data-Protection-Skills. Implements CPRA Section 1798.135 opt-out preference signal handling, covering Global Privacy Control (GPC) technical detection, automated signal honoring, cross-device consistency, and the relationship between browser signals and explicit consumer choices. Activate for GPC, opt-out preference signal, CPRA 1798.135, browser privacy signal, Do Not Sell queries.
Its SKILL.md is about 2k 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 and Responsive design. 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 Privacy and GDPR
- Tasks that involve Responsive design
Example prompts
- “Use the cpra-opt-out-signals skill to implement CPRA Section 1798.135 opt-out preference signal handling, covering Global Privacy Control (GPC)…”
- “/cpra-opt-out-signals”
Requirements
- Python 3
Workflow steps
7 steps, taken from the step headings in SKILL.md.
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
Cpra Opt Out Signals loads about 2k tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 96 tokens; SKILL.md has 871 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.
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). 871 words, ~1,960 tokens.
Download SKILL.mdSave it as
.claude/skills/cpra-opt-out-signals/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- cpra-opt-out-signals
- description
- Implements CPRA Section 1798.135 opt-out preference signal handling, covering Global Privacy Control (GPC) technical detection, automated signal honoring, cross-device consistency, and the relationship between browser signals and explicit consumer choices. Activate for GPC, opt-out preference signal, CPRA 1798.135, browser privacy signal, Do Not Sell queries.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- data-subject-rights
- metadata.tags
- opt-out-preference-signal, gpc, cpra, global-privacy-control, do-not-sell
Implementing CPRA Opt-Out Preference Signals
Overview
CPRA Section 1798.135 requires businesses to treat opt-out preference signals (such as Global Privacy Control / GPC) as valid consumer requests to opt out of the sale and sharing of personal information. This skill covers the technical detection of GPC signals, automated honoring workflows, cross-device consistency requirements, and the interaction between browser-level signals and explicit consumer choices.
Legal Foundation
CPRA Section 1798.135 — Methods of Limiting Sale, Sharing, and Use
Section 1798.135(a) — A business that sells or shares consumers' personal information shall provide a clear and conspicuous link on its homepage titled "Do Not Sell or Share My Personal Information."
Section 1798.135(b)(1) — A business that sells or shares personal information shall treat the consumer's use of an opt-out preference signal as a valid request to opt out under Section 1798.120.
Section 1798.135(b)(3) — A business that complies with subsection (b)(1) is not required to post the "Do Not Sell or Share My Personal Information" link on its homepage, provided it instead posts a link to a page describing the consumer's opt-out rights.
Section 1798.135(e) — A business may not interpret the absence of an opt-out preference signal as consent to sell or share personal information.
CCPA Regulations (11 CCR Section 7025)
- Section 7025(a) — A business shall process an opt-out preference signal as a valid request to opt out of sale/sharing for that browser or device, and, if known, the consumer.
- Section 7025(b) — If the business is unable to identify the consumer, the opt-out shall apply to the browser or device from which the signal was sent.
- Section 7025(c) — The business shall not require the consumer to provide additional information to opt out via a preference signal, unless necessary to verify the consumer's identity.
- Section 7025(d) — If a conflict exists between the opt-out preference signal and a consumer's business-specific privacy setting, the business shall process the opt-out preference signal but may notify the consumer of the conflict and provide the consumer the opportunity to confirm their intention.
Global Privacy Control (GPC) Specification
GPC is an HTTP header and JavaScript API signal that communicates a user's privacy preferences:
- HTTP header:
Sec-GPC: 1 - JavaScript API:
navigator.globalPrivacyControl === true - DNT header: GPC is distinct from the deprecated Do Not Track (DNT) header. GPC has legal effect under CPRA and Colorado Privacy Act; DNT does not.
Technical Implementation
Step 1: Detect the GPC Signal
Server-Side Detection
Check for the GPC HTTP header on every incoming request:
HTTP Header: Sec-GPC: 1If the header is present and its value is 1, the user has activated GPC.
Client-Side Detection (JavaScript)
For single-page applications or client-side consent management:
if (navigator.globalPrivacyControl === true) {
// GPC signal detected — treat as opt-out of sale/sharing
}Step 2: Map GPC Signal to Consumer
| Scenario | Action |
|---|---|
| Consumer is logged in (authenticated) | Apply opt-out to the consumer's account across all devices |
| Consumer is not logged in but has cookies | Apply opt-out to the browser/device |
| Consumer is anonymous (no identification) | Apply opt-out to the current browsing session and device |
Show full SKILL.md (390 more words)Show less
Step 3: Automated Honoring
When a GPC signal is detected, the following actions must be executed automatically:
- Suppress third-party tracking scripts: Do not load advertising pixels, third-party analytics trackers, or cross-site tracking scripts.
- Disable advertising cookies: Do not set or read cookies used for targeted advertising or cross-context behavioral advertising.
- Exclude from data sharing: Do not include the user's data in any data-sharing arrangements with third parties for advertising or monetisation purposes.
- Exclude from sale: Do not sell the user's personal information to any third party.
- Update consent management platform: Set the user's sale/sharing preference to "opted-out" in the CMP.
Step 4: Consent Management Platform (CMP) Integration
The CMP must be configured to:
- Detect GPC on page load: Before any third-party scripts are loaded.
- Suppress consent banner sale/sharing options: If GPC is detected, automatically set the sale/sharing toggle to "opted-out" and suppress any request for consent to sell/share.
- Allow explicit re-consent: If the consumer explicitly chooses to opt back in through the business's privacy settings, this explicit choice overrides the GPC signal for that business only.
- Log the signal: Record the GPC signal detection for compliance audit purposes.
Step 5: Cross-Device Consistency
| Consumer Status | Cross-Device Behaviour |
|---|---|
| Authenticated (logged-in account) | GPC signal from one device triggers account-level opt-out across all devices |
| Unauthenticated | GPC signal applies only to the device/browser from which it was sent |
| Consumer later logs in from GPC-enabled device | Account-level opt-out is applied retroactively |
Step 6: Conflict Resolution
When a conflict exists between the GPC signal and the consumer's explicit business-specific setting:
[GPC Signal Detected: Opt-Out]
│
▼
[Does consumer have an explicit business-specific setting?]
│
├── No explicit setting ──► Honor GPC signal (opt-out)
│
├── Explicit opt-in to sale/sharing ──► [Conflict]
│ └── Honor GPC signal (opt-out applies)
│ Optionally: display notification
│ "Your browser is sending a Global Privacy Control signal.
│ We have applied this as an opt-out of sale/sharing.
│ You previously opted in to sale/sharing on this site.
│ If you wish to maintain your opt-in, please confirm
│ in your privacy settings."
│
└── Explicit opt-out ──► No conflict (both agree on opt-out)Step 7: Documentation and Audit
- Log every GPC signal detection with timestamp, IP hash, device identifier, and authenticated status.
- Log every opt-out action taken in response to a GPC signal.
- Maintain records for 24 months per CCPA regulation requirements.
- Include GPC signal handling in quarterly privacy compliance audits.
- Test GPC detection quarterly using browsers with GPC enabled (Firefox, Brave, DuckDuckGo).
Monitoring and Testing
Monthly Verification Checklist
- GPC header detection confirmed operational (test with Sec-GPC: 1)
- JavaScript API detection confirmed operational (test with navigator.globalPrivacyControl)
- Third-party tracking scripts are suppressed when GPC is detected
- Advertising cookies are not set when GPC is detected
- CMP correctly reflects GPC opt-out status
- Cross-device consistency confirmed for authenticated users
- Conflict resolution functioning as designed
- Audit logs recording GPC detections
© 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/cpra-opt-out-signals 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
Cpra Opt Out Signals 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 |
|---|---|---|---|---|---|---|
| Cpra Opt Out Signals this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~2k | 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 |
Similar skills
HIPAA Safe Harbor Coverage Audit
maziyarpanahi/openmed
Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.
Korean Privacy Terms
kimlawtech/korean-privacy-terms
처리방침·이용약관 자동 생성 스킬 패키지 (v4.0). An agent skill from kimlawtech/korean-privacy-terms.
Gdpr Compliance
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…
Hipaa Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert HIPAA compliance assistant for healthcare and software contexts.
Pii Contract Analyze
gregmos/PII-Shield
Universal legal document processor with PII anonymization. An agent skill from gregmos/PII-Shield.
More from mukul975/Privacy-Data-Protection-Skills
All 280 skills in this repoAge Gating Services
mukul975/Privacy-Data-Protection-Skills
Implements age-gating mechanisms for online services to restrict access based on user age.
AI Data Retention
mukul975/Privacy-Data-Protection-Skills
Manages AI model retention and machine unlearning requirements.
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.
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).
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.
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.
Related
Categories
Questions about Cpra Opt Out Signals
What does Cpra Opt Out Signals do?
Implements CPRA Section 1798.135 opt-out preference signal handling, covering Global Privacy Control (GPC) technical detection, automated signal honoring, cross-device consistency, and the…. Cpra Opt Out Signals is an agent skill from mukul975/Privacy-Data-Protection-Skills.135 opt-out preference signal handling, covering Global Privacy Control (GPC) technical detection, automated signal honoring, cross-device consistency, and the relationship between browser signals and explicit consumer choices.
When should I use Cpra Opt Out Signals?
Cpra Opt Out Signals fits situations like: tasks that involve Privacy and GDPR; tasks that involve Responsive design.
How do I install Cpra Opt Out Signals in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill cpra-opt-out-signals -a claude-code`. Or copy the skill folder (skills/privacy/cpra-opt-out-signals in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/cpra-opt-out-signals in your project. Claude Code loads it when a task matches its description.
How do I install Cpra Opt Out Signals in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill cpra-opt-out-signals -a codex`. Or copy the skill folder (skills/privacy/cpra-opt-out-signals in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/cpra-opt-out-signals in your project. Codex loads it when a task matches its description.
Can I use Cpra Opt Out Signals 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 cpra-opt-out-signals -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cpra-opt-out-signals, .gemini/skills/cpra-opt-out-signals, .github/skills/cpra-opt-out-signals and .opencode/skills/cpra-opt-out-signals in your project.
What does Cpra Opt Out Signals need to run?
Going by SKILL.md and its folder, Cpra Opt Out Signals needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Cpra Opt Out Signals 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 Cpra Opt Out Signals 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 Cpra Opt Out Signals use?
Cpra Opt Out Signals 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 Cpra Opt Out Signals use?
About 2k tokens (SKILL.md is roughly 7.8k 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 1.4k tokens, read only when the agent opens those files.
What are the alternatives to Cpra Opt Out Signals?
Skills that share tags, products or a category with Cpra Opt Out Signals: 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.
Who maintains Cpra Opt Out Signals?
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.