evidence-hygiene
From the author
Sanitize security evidence before sharing, reporting, or writing up findings. Use for bug bounty reports, guided MCP assessments, pentest/DFIR notes, screenshots, HAR files, curl commands, request/response logs, PoC output, terminal transcripts, writeups, and any evidence that may contain cookies, bearer tokens, API keys, session IDs, PII, customer data, credentials, internal hostnames, or excessive exploit output.
Install
npx skills add 26zl/cybersec-toolkit --skill evidence-hygiene -a claude-code
Installs to .claude/skills/evidence-hygiene/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- evidenceEncod3d-Sec/TORCHEvidence hygiene before any FIND moves to Completed or enters a report. Cookie redaction, PII black-bar, HAR sanitization, screenshot metadata strip. Run after /triage passes and before final report assembly.Other★ 335
- credential-exposure-auditzero-lab-ai/skillsAudits supplied evidence when passwords, hashes, private keys, browser or vault entries, cloud CLI credentials, application secrets, tokens, or credential-bearing artifacts may be exposed. Use for defensive review that must distinguish indicators from material and validity from privilege without decrypting, cracking, replaying, or authenticating.Browser★ 282
- content-sanitizationathola/claude-night-marketProvides sanitization guidelines for external content in skills and hooks. Use when loading GitHub Issues, PRs, WebFetch results, or any untrusted input.Other★ 343
- logging-and-monitoring-evidence-packbetter-isms/grcskillsUse this skill when an auditor, customer or regulator will ask how security events are logged and watched, and someone says "prepare logging evidence", "show we monitor alerts", "what do we log and for how long", "who looks at the SIEM", "prove an alert was handled" or "our monitoring evidence is just dashboard screenshots". Maps log coverage and retention per system, lists the alert rules that matter and where they go, traces real alerts end to end with timestamps, and writes an evidence pack with the gaps stated plainly.Security★ 51
- bug-reviewathola/claude-night-marketHunts bugs with evidence trails. Use when investigating unexpected behavior or before merging code with potential hidden defects.Engineering★ 343
- finding-disciplinehypnguyen1209/offensive-claudeUse when about to record, claim, rate the severity of, or report any security finding — before marking anything [CONFIRMED] or writing it into the reportSecurity★ 401
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in