Evidence Hygiene

Evidence Hygiene is an AI Engineering skill for Claude Code, published by elementalsouls in Claude-BugHunter.

3.6K stars559 forkson elementalsouls/Claude-BugHunterAdded 2026/08/16+3% in starsRepository updated 2026/08/16

ai-securityanthropicapplication-securitybug-bountybugbountybugcrowdclaudeclaude-codeclaude-skillsethical-hackinghackeroneoffensive-securitypentestingred-teamsecurity-toolsweb-security

Install in seconds

Install Evidence Hygiene

Copy Evidence Hygiene into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/elementalsouls/Claude-BugHunter/tree/main/skills/evidence-hygiene ~/.claude/skills/evidence-hygiene

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/elementalsouls/Claude-BugHunter.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: skills/evidence-hygiene/SKILL.md in elementalsouls/Claude-BugHunter
Installs to: ~/.claude/skills/evidence-hygiene
Collection: One of 25 skills cataloged from this repository
Category: AI Engineering — 2451 skills

What Evidence Hygiene does

Evidence Hygiene guides redaction of cookies, PII, and HAR files in bug-bounty evidence capture, ensuring sessions and user data are protected before screenshots or attachments are shared. Use it before any PoC capture to avoid leaking secrets.

Evidence Hygiene is cataloged under AI Engineering on DirSkills. Evidence Hygiene comes from a repository tagged ai-security, anthropic, application-security, bug-bounty and bugbounty.

Documentation

README

Excerpt

EVIDENCE HYGIENE — PoC Capture & Redaction Discipline

Use this skill BEFORE capturing any screenshot, exporting any HAR, or attaching any evidence to a bug-bounty submission. It catches the most common evidence-hygiene mistakes that cause cookies to leak, PII to be shared without consent, or screenshots to be unsuitable for triage.

The core principle: Bug-bounty evidence is meant to convince a triager. Anything beyond that — live cookies, real-user PII, internal trace IDs that aren't useful — should not be in the evidence.

1. Two Categories of Sensitive Data

Every PoC artifact (screenshot, HAR, raw HTTP request, terminal transcript) potentially contains data that needs different treatment.

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Evidence Hygiene

What else does elementalsouls publish alongside Evidence Hygiene?
Evidence Hygiene is one of 25 skills that DirSkills catalogs from elementalsouls/Claude-BugHunter, the repository it ships in. Its siblings there include API Misconfig Hunter, APK Red Team Pipeline and Auth Bypass Hunting. Each one is a separate skill with its own page in this directory, installs the same way Evidence Hygiene does, and is maintained by elementalsouls in that same repository. The rest of the collection is listed on the elementalsouls/Claude-BugHunter page.
How does Evidence Hygiene compare to other AI Engineering skills?
Evidence Hygiene ranks #584 by stars among the 2451 AI Engineering skills in this catalog. The most-starred ones next to it are Architecture Decision Records, AI-First Engineering and Agentic OS. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Evidence Hygiene against them. Open each page to compare what they document and how they install.