privacy-guard

Scan code, configuration, and skill files for PII and secrets before processing.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/plutowang/term.conf --skill privacy-guard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: privacy-guard
Source: https://github.com/plutowang/term.conf/tree/main/opencode/skills/global/privacy-guard
Command: npx skills add https://github.com/plutowang/term.conf --skill privacy-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces zero-tolerance privacy scanning before code processing to prevent leakage of sensitive information such as PII and secrets.

Core Features & Use Cases

  • PII and secrets redaction: Automatically detect and redact keys, passwords, API keys, and personal data.
  • Strict allowlist enforcement: Only permit approved file types for processing (code, config, and skill documents).
  • Pre-processing gate: Block non-compliant artifacts from entering the build or analysis pipeline.
  • Use Case: Integrate into CI workflows to sanitize code commits and ensure compliant artifact delivery.

Quick Start

Add privacy guard to the pre-processing stage of your code pipeline and run a test sweep against a sample repository.

Frequently Asked Questions about privacy-guard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan code commits for PII and secrets before processing?

A zero-tolerance privacy scan for PII and secrets enforces strict redaction of keys, passwords, and personal data before code enters your pipeline. It blocks non-compliant artifacts from passing through the pre-processing gate.

How do I prevent sensitive data leakage in automated code review pipelines?

Preventing data leakage in automated code review pipelines requires a strict pre-processing gate that blocks unauthorized file types and redacts PII. This sanitizes commits and ensures only compliant artifacts enter the build.

Can I enforce an allowlist for approved file types in my CI workflow?

Yes, you can enforce strict allowlist rules in your CI workflow to permit only approved file types like code, config, and skill documents. This blocks unauthorized artifacts from entering the build pipeline.

What is a zero-tolerance privacy scan for code inputs?

A zero-tolerance privacy scan for code inputs is a strict pre-processing validation that detects and redacts PII, secrets, and unauthorized files. It ensures non-compliant artifacts never enter your processing pipelines.

Does privacy scanning work with configuration files and skill documents?

Yes, privacy scanning applies strict allowlist enforcement to configuration files and skill documents. It covers code, config, and skill files within development pipelines to sanitize commits and secure artifact delivery.