pii-guard

Scan outbound content for personal data and block transmission.

19|4|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/profbernardoj/morpheus-skill --skill pii-guard-profbernardoj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pii-guard
Source: https://github.com/profbernardoj/morpheus-skill/tree/main/skills/pii-guard
Command: npx skills add https://github.com/profbernardoj/morpheus-skill --skill pii-guard-profbernardoj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PII Guard prevents accidental personal-data exposure by checking outbound content before it leaves your workspace, helping you stop leaks in high-risk workflows like pushes, posts, messages, and publishing.

Core Features & Use Cases

  • Hard-block scanning: Detects protected names, emails, phone numbers, wallet addresses, organizations, websites, keywords, and custom regex patterns before external transmission.
  • Global git enforcement: Installs a pre-push hook that scans diffs across repositories on the machine and blocks pushes when sensitive data is found.
  • CLI and history checks: Scans files, directories, text input, stdin, and git history to catch both current leaks and older committed secrets.
  • Use Case: A developer is about to publish a change set containing a personal email address and wallet address; the scanner finds the match, reports it, and stops the push until the data is removed or explicitly overridden.

Quick Start

Run the setup script from the skill directory to create your personal patterns file, install the global pre-push hook, and enable leak scanning before outbound actions.

Frequently Asked Questions about pii-guard

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

FAQPage Schema
How do I prevent PII from leaking in git pushes?

To prevent PII from leaking in git pushes, you need a pre-push hook that scans diffs for sensitive data. This tool installs a global git hook that blocks pushes when personal data is detected, requiring removal or an explicit override to proceed.

How do I scan git history for committed personal data?

Scanning git history for committed personal data requires checking previous commits for exposed secrets. The tool provides CLI history checks to identify older committed emails, wallet addresses, and phone numbers alongside current file content.

Can I block sensitive data across multiple outbound workflows like email and publishing?

Yes, blocking sensitive data across multiple outbound workflows is supported. The scanner applies hard-block enforcement before external transmissions including email sending, social posting, GitHub interactions, file attachments, and web submissions.

What types of personal data can content scanning detect before transmission?

Content scanning detects protected names, emails, phone numbers, wallet addresses, organizations, websites, and keywords. Users can also configure custom regex patterns to catch specific personal data formats before they leave the workspace.

Does the pre-push hook support overrides for false positives?

Yes, the pre-push hook supports overrides for false positives. When the scanner finds a match and blocks the push, you can explicitly override the block to allow the transmission if the detected data is not actually sensitive.