Automated summary
This skill guides use of the ffind tool to identify file types inside a binary and extract the ext2/3/4 or F2FS filesystems it contains, typically during firmware analysis.
Strengths
- Security-artifact-oriented file type detection, with an -a flag to reveal all common formats
- Built-in extraction of ext2/3/4 and F2FS filesystems to a timestamped or custom directory
- Three output formats (text, json, quiet) suitable for human review or automated pipelines
- Accepts multiple paths in one invocation to analyze several binaries at once
Limitations
- Extraction requires sudo/root, which limits use in restricted environments
- Depends on external tools that must be installed: e2fsprogs, f2fs-tools and util-linux
- Only covers ext2/3/4 and F2FS; no support described for other filesystem formats
Use it when you need to inspect a firmware or binary image, identify the file types it contains, or unpack an embedded ext/F2FS partition.
Avoid it when you lack root privileges or the e2fsprogs/f2fs-tools packages, or when the image uses an unsupported filesystem.
Security analysis
CautionThe skill is a legitimate firmware-analysis helper, but it instructs use of sudo and an external `ffind` binary for filesystem extraction. There is no evidence of destructive behavior, credential exfiltration, obfuscation, or disabling safety controls, but the privileged execution and filesystem-writing capabilities warrant caution.
- •Requires sudo/root privileges for filesystem extraction
- •Runs an external `ffind` binary from an unspecified iothackbot bin directory, so trust depends on that tool
- •Uses bash commands and external utilities (e2fsprogs, f2fs-tools, util-linux) for filesystem handling
- •No explicit safeguards or path validation around extraction output locations
Examples
Analyse le firmware /tmp/router-fw.bin avec ffind et dis-moi quels types de fichiers il contient.Extrais tous les systèmes de fichiers du firmware /tmp/router-fw.bin avec sudo ffind -e et liste ce qui a été récupéré.Lance ffind sur /tmp/a.bin et /tmp/b.bin avec -a et --format json, puis résume les types de fichiers détectés.name: ffind description: 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.
Ffind - Advanced File Finder with Extraction
You are helping the user find and analyze files with advanced type detection and optional filesystem extraction capabilities using the ffind tool.
Tool Overview
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.
Instructions
When the user asks to analyze files, find specific file types, or extract filesystems:
-
Understand the target:
- Ask what path(s) they want to analyze
- Determine if they want to extract filesystems or just analyze
- Ask if they want all file types or just artifact types
-
Execute the analysis:
- Use the ffind command from the iothackbot bin directory
- Basic usage:
ffind <path> [<path2> ...] - To extract filesystems:
ffind <path> -e - Custom extraction directory:
ffind <path> -e -d /path/to/output - Show all file types:
ffind <path> -a - Verbose output:
ffind <path> -v
-
Output formats:
--format text(default): Human-readable colored output with type summaries--format json: Machine-readable JSON--format quiet: Minimal output
-
Extraction capabilities:
- Supports ext2/ext3/ext4 filesystems (requires e2fsprogs)
- Supports F2FS filesystems (requires f2fs-tools)
- Requires sudo privileges for extraction
- Default extraction location:
/tmp/ffind_<timestamp>
Examples
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
Important Notes
- Extraction requires root/sudo privileges
- Requires external tools: e2fsprogs, f2fs-tools, util-linux
- Identifies "artifact" file types relevant to security analysis by default
- Use
-aflag to see all file types including common formats
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/advanced-file-finder-with-extraction-mrzxuqiu/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/advanced-file-finder-with-extraction-mrzxuqiu' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/advanced-file-finder-with-extraction-mrzxuqiu/download' --output '.skill-downloads/advanced-file-finder-with-extraction-mrzxuqiu/SKILL.md.part' && mv '.skill-downloads/advanced-file-finder-with-extraction-mrzxuqiu/SKILL.md.part' '.skill-downloads/advanced-file-finder-with-extraction-mrzxuqiu/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/advanced-file-finder-with-extraction-mrzxuqiu/SKILL.md' && test -s '.skill-downloads/advanced-file-finder-with-extraction-mrzxuqiu/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/ffind' && cp -R '.skill-downloads/advanced-file-finder-with-extraction-mrzxuqiu' '.claude/skills/ffind'Cursor
test -f '.skill-downloads/advanced-file-finder-with-extraction-mrzxuqiu/SKILL.md' && test -s '.skill-downloads/advanced-file-finder-with-extraction-mrzxuqiu/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/ffind' && cp -R '.skill-downloads/advanced-file-finder-with-extraction-mrzxuqiu' '.cursor/skills/ffind'Codex
test -f '.skill-downloads/advanced-file-finder-with-extraction-mrzxuqiu/SKILL.md' && test -s '.skill-downloads/advanced-file-finder-with-extraction-mrzxuqiu/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/ffind' && cp -R '.skill-downloads/advanced-file-finder-with-extraction-mrzxuqiu' '.agents/skills/ffind'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/advanced-file-finder-with-extraction-mrzxuqiu'openskills read 'advanced-file-finder-with-extraction-mrzxuqiu'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/advanced-file-finder-with-extraction-mrzxuqiu/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
DeFi AMM Security
Security
Security checklist for Solidity AMM contracts, liquidity pools, and swap flows. Covers reentrancy, donation attacks, oracle manipulation, slippage, and integer math.
Semgrep Rule Creator
Security
Creates custom Semgrep rules for detecting security vulnerabilities, bug patterns, and code patterns. Includes test-first methodology, taint mode support, and validation steps. Helps when building targeted static analysis detections.
Dev Toolbar Review Guide
Security
Safety rules for the dev toolbar, PostHog client, and feature flags. Use when reviewing changes to dev-tools and related files, covering environment guards, override cookies, and SSE stream safety.