Agent Log Secrets Scanner
$1.99OfficialUse to scan agent transcripts, traces, and telemetry for leaked secrets or PII before they are stored or shared, and to fix the root cause.
securitysecretspiiobservabilityredactionincident-responseagent-logs· by SkillingMain
What you get
- ✓12-step procedure
- ✓Runnable Python included
- ✓9-point quality checklist
- ✓8 pitfalls to avoid
- ✓Installs into 6 tools
- Version
- v1 →
- Last updated
- today
- Length
- 11 min read
- Requires
- Works with any modern AI assistant
Works in: Claude Code, Codex, Cline, opencode, OpenClaw, Hermes · Built for large codebases
Preview
When to use
Invoke this skill when you must scan agent output for leaked secrets or PII, or prove that none leaked, before that output is stored, shared, or reused. Concrete triggers:
- Before exporting or sharing a session transcript, support bundle, replay file, or debugging export with anyone outside the trust boundary.
- After the agent ran a command that can dump credentials to stdout (
env,printenv,cat .env,aws configure list,kubectl get secret -o yaml,docker inspect,terraform show) and the framework logged the full output. - When a trace backend (OpenTelemetry
gen_ai.*spans, LangSmith, Langfuse, Honeycomb) is capturing full prompt and completion content, whi
…
🔒 Buy once ($1.99) to unlock the full playbook, download it, and install it in every tool you use.