← Browse

@yv1ing/binwalk

A

Use binwalk for authorized firmware, binary blob, archive, filesystem, and embedded-content triage with bounded extraction and evidence handling.

skillclaude

Install

agr install @yv1ing/binwalk --target claude

Writes 1 file into .claude/skills/, pinned to git-df4b2185.

  • .claude/skills/binwalk/SKILL.md

Document


name: binwalk description: Use binwalk for authorized firmware, binary blob, archive, filesystem, and embedded-content triage with bounded extraction and evidence handling.

binwalk

Use binwalk for authorized triage of firmware images, binary blobs, packed artifacts, and files that may contain embedded filesystems or compressed content.

Help First

Before constructing commands, run the installed help and use it as the source of truth:

binwalk --help

Usage Rules

  • Work only on explicitly provided artifacts in scope.
  • Start with identification/listing before extraction.
  • Extract only into a task-scoped output directory.
  • Treat signatures and offsets as leads; verify extracted files with file, hashes, directory review, or follow-up analysis.
  • Keep extraction bounded and avoid recursive or broad extraction unless the user explicitly asks and the artifact scope permits it.
  • Do not execute extracted files.
  • Save large listings, extraction logs, and recursive output to files rather than streaming them into the conversation.

Common Workflows

Signature scan without extraction:

binwalk firmware.bin

Bounded extraction into a task directory:

mkdir -p binwalk-out
binwalk -e -C binwalk-out firmware.bin

Review extracted file types before further analysis:

find binwalk-out -maxdepth 3 -type f -exec file '{}' +

Use recursive extraction only when the artifact scope and expected expansion are clear:

binwalk -Me -C binwalk-out firmware.bin

Output

Report the artifact path, command used, output directory, notable offsets or embedded content, extracted paths, and limitations such as failed extraction or unsupported formats.

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-df4b21851ba62026-07-31