Is the Chipsec skill free?

Yes. The skill itself is free from BrownFineSecurity/iothackbot. SkillProof publishes the install command and an independent test verdict at no cost.

What is the Chipsec SkillProof Score?

7.6/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 5/10, docs & honesty 4/5.

How do I install Chipsec?

Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.

Can I use Chipsec with Cursor, Copilot, Gemini CLI, Codex or other AI tools?

The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.

Chipsec

Static UEFI/BIOS firmware analysis via Intel chipsec: scan dumps for known rootkits

by BrownFineSecurity · BrownFineSecurity/iothackbot

Works with setup

Install — copy the command Download source ↗

Test report

Verdict: Works with setup
Score: 7.6/10
Tested: Jul 21, 2026
Environment: Claude Code 2.x (agent harness)
Upstream re-checked: Aug 10, 2026 · 6c5fdeb

Located skills/chipsec/SKILL.md via the GitHub tree API and fetched it raw. Frontmatter parses with name+description (389 chars); the skill is a single file with no repo-internal helper scripts, so nothing was broken to spot-check, and it derives CHIPSEC_DIR dynamically (no hardcoded paths). Confirmed chipsec is absent (chipsec_main not found; pip show chipsec = not found) and I had no firmware dump, so no artifact could be produced — output is unmeasurable. Only smell noted: sudo chmod 777 on chipsec's logs dir, a known logging-permission workaround, not exfiltration.

Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works

Installs cleanly 5/5
Triggers reliably 5/5
Output vs. baseline 5/10
Docs & honesty 4/5

What Chipsec does

Wraps Intel's chipsec framework to statically analyze UEFI/BIOS firmware dumps offline: scans .bin/.rom/.fd/.cap images for known rootkits (LoJax, ThinkPwn, HackingTeam, MosaicRegressor) and SMM vulnerabilities, generates hashed EFI executable inventories, decodes firmware structure, and extracts NVRAM variables. Triggers when analyzing firmware dump files for known implants or building a baseline without hardware access. Requires the chipsec CLI (pip install chipsec) and a firmware image to operate on.

How to install Chipsec

git clone --depth 1 https://github.com/BrownFineSecurity/iothackbot.git /tmp/chipsec-src
mkdir -p ~/.claude/skills
cp -R /tmp/chipsec-src/skills/chipsec ~/.claude/skills/chipsec
# Requires the external chipsec CLI (not bundled): pip install chipsec
#   provides chipsec_main and chipsec_util
# One-time logs-dir fix (see SKILL.md): derive CHIPSEC_DIR under site-packages, mkdir logs, chmod
# Needs a UEFI/BIOS firmware dump (.bin/.rom/.fd/.cap) as analysis input
# Primary command: chipsec_main -i -n -m tools.uefi.scan_blocked -a <firmware.bin>

Skills live in ~/.claude/skills/ (global) or .claude/skills/ (per-project). Restart Claude Code after installing.

Commands — how to trigger Chipsec

/chipsec Static UEFI/BIOS firmware analysis via Intel chipsec: scan dumps for known rootkits

It also activates on plain-language prompts like these:

Scan this firmware.bin for known rootkits
Extract NVRAM variables from this BIOS dump
Parse the SPI flash descriptor in this .rom file

Frequently asked questions

Is the Chipsec skill free?: Yes. The skill itself is free from BrownFineSecurity/iothackbot. SkillProof publishes the install command and an independent test verdict at no cost.
Does Chipsec work with Claude Code?: We tested it with Claude Code 2.x (agent harness) on Jul 21, 2026. Verdict: Works with setup. Located skills/chipsec/SKILL.md via the GitHub tree API and fetched it raw. Frontmatter parses with name+description (389 chars); the skill is a single file with no repo-internal helper scripts, so nothing was broken to spot-check, and it derives CHIPSEC_DIR dynamically (no hardcoded paths). Confirmed chipsec is absent (chipsec_main not found; pip show chipsec = not found) and I had no firmware dump, so no artifact could be produced — output is unmeasurable. Only smell noted: sudo chmod 777 on chipsec's logs dir, a known logging-permission workaround, not exfiltration.
What is the Chipsec SkillProof Score?: 7.6/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 5/10, docs & honesty 4/5.
How do I install Chipsec?: Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
Can I use Chipsec with Cursor, Copilot, Gemini CLI, Codex or other AI tools?: The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.