Log redaction auditor

Skill sisodiabhumca/agent-skills/skills/log-redaction-auditor

Production-Ready Agent Skills : product analytics, growth experiments, CRM, research synthesis, postmortems, data contracts, SaaS spend, compliance, architecture maps, and LLM eval and many more.

Install

npx -y skills add sisodiabhumca/agent-skills --skill log-redaction-auditor

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Vendor-neutral skill to audit application logs for potential sensitive-data leakage and redaction coverage.

SKILL.md

1.2 KB, as published. Nobody here has run it

When to invoke

You have application logs (text) and want to check whether secrets/PII might be present.
You want a repeatable, automated check in CI/CD before sharing logs externally.

Inputs needed

--input path to a log file (UTF-8 text).
Optional: --config path to a JSON config overriding patterns and allowlists.

Workflow

Scan log lines with conservative rules for likely secrets/PII.
Apply allowlists (known test keys/domains) to reduce false positives.
Emit a JSON report with counts, examples, and line numbers.

Output format

JSON written to --output with:
- summary: counts by severity and rule.
- findings: list of matches with severity, rule_id, line_number, match, and context.

Guardrails

Do not modify the input logs.
Avoid printing raw secrets to stdout; only write to output file.
Provide an allowlist mechanism to reduce false positives.

Reference code

log_redaction_auditor.py implements the scanner using Python stdlib regex + JSON.