brownfinesecurity
Advanced file finder with type detection and filesystem extraction for analyzing firmware and extracting embedded filesystems. Use when you need to analyze firmware files, identify file types, or extract ext2/3/4 or F2FS filesystems.
bunx add-skill brownfinesecurity/iothackbot -s ffindLoadingβ¦
You are helping the user find and analyze files with advanced type detection and optional filesystem extraction capabilities using the ffind tool.
Ffind analyzes files and directories, identifies file types, and can extract filesystems (ext2/3/4, F2FS) for deeper analysis. It's designed for firmware and IoT device analysis.
When the user asks to analyze files, find specific file types, or extract filesystems:
Understand the target:
Execute the analysis:
ffind <path> [<path2> ...]ffind <path> -effind <path> -e -d /path/to/outputffind <path> -affind <path> -vOutput formats:
--format text (default): Human-readable colored output with type summaries--format json: Machine-readable JSON--format quiet: Minimal outputExtraction capabilities:
/tmp/ffind_<timestamp>Analyze a firmware file to see file types:
ffind /path/to/firmware.bin
Extract all filesystems from a firmware image:
sudo ffind /path/to/firmware.bin -e
Analyze multiple files and show all types:
ffind /path/to/file1.bin /path/to/file2.bin -a
Extract to a custom directory:
sudo ffind /path/to/firmware.bin -e -d /tmp/my-extraction
-a flag to see all file types including common formatsUse when you need to run Flow type checking, or when seeing Flow type errors in React code.
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.
Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.