log-pii-scanner

Name: log-pii-scanner
Availability: InStock
Author: mccode415

Detects potentially sensitive data in logs and flags it for review.

Updated Jan 27, 2026

Search Tags:#compliance #security audit #grep #pii #data leak #log scanning

Ready to run

npx skills add https://github.com/mccode415/agent --skill log-pii-scanner

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: log-pii-scanner
Source: https://github.com/mccode415/agent/tree/main/skills/log-pii-scanner
Command: npx skills add https://github.com/mccode415/agent --skill log-pii-scanner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps identify and prevent sensitive Personally Identifiable Information (PII) from being leaked in application log files, enhancing security and compliance.

Core Features & Use Cases

PII Detection: Scans log files for patterns matching SSNs, credit card numbers, emails, phone numbers, account numbers, and names.
Severity Assessment: Categorizes findings into High, Medium, and Low severity based on the type of PII detected.
Use Case: After a new feature is deployed that involves user data, run this skill to audit the application logs and ensure no sensitive customer information was accidentally logged.

Quick Start

Scan the log files in your user's Library directory for potential PII leaks.

Frequently Asked Questions about log-pii-scanner

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

FAQPage Schema

How do I scan application log files for PII leaks?▼

Scanning application log files for PII involves searching directories like ~/Library/Logs and ~/Library/Application Support/*/logs for sensitive data. The process uses Bash and Grep to identify exposed emails, phone numbers, SSNs, and account numbers.

What types of sensitive data are detected during a log security audit?▼

During a log security audit, detected sensitive data includes SSNs, credit card numbers, emails, phone numbers, account numbers, names, and addresses. These findings are classified into High, Medium, and Low severity levels based on the matched regex patterns.

How do I check macOS logs for sensitive data exposure after a new feature deployment?▼

Checking macOS logs for sensitive data exposure involves scanning ~/Library/Logs and ~/Library/Application Support/*/logs directories. This verifies whether newly deployed features accidentally logged customer PII such as SSNs, emails, or account numbers.

Does log scanning for PII work on any operating system?▼

This log scanning tool for PII is designed for macOS environments, specifically targeting predefined directories like ~/Library/Logs and ~/Library/Application Support/*/logs. It relies on Bash and Grep tools to execute the regex pattern matching.

What is the best way to prevent sensitive information from leaking in application logs?▼

To prevent sensitive information leaks in application logs, perform an automated audit using Bash and Grep to scan for PII patterns. This identifies SSNs, emails, and phone numbers, categorizing findings by severity to enhance security and compliance.