Skip to content
SkillModel-led4,159 tokens in use

evidence-hygiene

Redaction rules for bug bounty proof: what to mask in cookies, headers and other users' data, how to sanitize HAR files and in what order to capture screenshots.

14,523 stars on the repository MIT Licenseelementalsouls/Claude-BugHunter · skills/evidence-hygiene
/plugin marketplace add elementalsouls/Claude-BugHunter /plugin install claude-bughunter@elementalsouls
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing evidence-hygiene costs

190tokens idle
4,159tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetectednetworkdetectedwrites filesdetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter12/15
  • Structure25/25
  • Examples15/15
  • Output15/15
  • Size13/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Good
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 149
  • Writes files−8

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 164
  • Reaches the network−10

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 233

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity100
  • Maintenance84
  • Community68
  • Maturity28
  • Momentum40

evidence-hygiene is a skill for Claude to use before capturing a screenshot, exporting a HAR file or attaching any proof to a bug bounty submission. It sorts sensitive material into your own account secrets, other users’ personal data, metadata a triager finds useful and throwaway test passwords, and gives each a treatment.

It covers a cookie redaction protocol, a black-bar protocol for personal data, HAR sanitization, Burp Suite screenshot hygiene, browser console proof-of-concept patterns, capture order and steps to take after submission. The goal is evidence that convinces a triager without leaking live sessions or real people’s data.

What You Get

  • A table that sorts evidence data into four categories with a treatment for each
  • A cookie and header redaction protocol with redaction methods ranked by practicality
  • A black-bar protocol for names, emails, phone numbers and faces in other users’ data
  • HAR sanitization steps with a check that no cookie or authorization values remain
  • Guidance on Burp screenshots, console proof patterns, capture order and post-submission cleanup

Common Use Cases

  • Preparing screenshots for a bug bounty report that touches another user’s account data
  • Exporting a HAR file for a triager without leaking session tokens
  • Rotating test credentials and sessions after a report is filed

What Makes It Unique

It focuses on the narrow task of what evidence to show and what to hide, and it separates your own secrets from other people’s data with different rules for each. It also lists what to leave visible, such as trace identifiers, because those help triagers match logs.

Under The Hood

The skill is a single SKILL.md of guidance with no bundled scripts. It tells the agent how to handle screenshots, HAR files and request captures. It includes a shell function that rewrites an exported HAR file with redacted cookie and header values and a check for leftovers, so the agent may read and write files in the working folder. It also shows a browser-console fetch example for proof-of-concept requests, which sends a request from the browser to the target when run. Use it only on evidence from assets you are authorized to test.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers