Borrowing it
Nothing to install: this file belongs to Suzu-Testing/metasploit-cursor-harness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Suzu-Testing/metasploit-cursor-harness/main/.cursor/skills/hardware-pentest/SKILL.mdgit clone --depth 1 https://github.com/Suzu-Testing/metasploit-cursor-harnessWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/suzu-testing/metasploit-cursor-harness/hardware-pentest)<a href="https://agentmods.dev/skills/suzu-testing/metasploit-cursor-harness/hardware-pentest"><img src="https://agentmods.dev/badge/skills/suzu-testing/metasploit-cursor-harness/hardware-pentest/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/suzu-testing/metasploit-cursor-harness/hardware-pentest"><img src="https://agentmods.dev/badge/skills/suzu-testing/metasploit-cursor-harness/hardware-pentest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00046 | $0.01340 |
| Opus 5 | $0.00023 | $0.00670 |
| Sonnet 5 | $0.00009 | $0.00268 |
| Haiku 4.5 | $0.00005 | $0.00134 |
Grade A, and why
hardware-pentest scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hardware Pentest
Prerequisites
- Physical access and hardware testing require explicit ROE authorization.
- Device ownership or written permission for destructive extraction (chip-off, flash dump).
- ESD-safe workspace and appropriate programmers (CH341A, Bus Pirate, J-Link).
Workflow
Task Progress:
- [ ] Confirm physical access scope and device inventory
- [ ] Gather OSINT (datasheets, FCC IDs, open-source components)
- [ ] Acquire firmware (download, OTA intercept, UART/JTAG/SPI dump)
- [ ] Extract and analyze filesystem (binwalk, strings)
- [ ] Identify hardcoded creds, backdoors, and attack surface
Phase 1: OSINT and reconnaissance
Information gathering
MSF: No direct module. Use OSINT sources and CLI triage.
CLI fallback:
strings firmware.bin | grep -iE "version|copyright|build"
binwalk firmware.bin
file firmware.bin
# FCC ID lookup, vendor firmware pages, Shodan/Censys for exposed interfaces
Phase 2: Physical access attacks
BIOS/UEFI and live access
MSF: No direct module. Use physical access techniques.
CLI fallback:
# Default BIOS passwords, CMOS battery reset, live USB boot
# SAM editing, single-user mode / init=/bin/sh on Linux
HID implants
MSF: No direct module. Use Rubber Ducky/BadUSB payloads.
CLI fallback:
# Rubber Ducky / BadUSB keystroke injection
# Bash Bunny for network attacks from USB form factor
Phase 3: Debug interface identification
UART
MSF: No direct module. Use serial console tools.
CLI fallback:
baudrate -f /dev/ttyUSB0
screen /dev/ttyUSB0 115200
# USB-TTL adapter, multimeter for GND/TX identification
JTAG
MSF: No direct module. Use OpenOCD.
CLI fallback:
openocd -f interface/jlink.cfg -f target/stm32f1x.cfg
# JTAGulator for pin identification
SPI flash
MSF: No direct module. Use flashrom.
CLI fallback:
flashrom -p ch341a_spi -r firmware_dump.bin
flashrom -p buspirate_spi:dev=/dev/ttyUSB0 -r dump.bin
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 206 lines · 46 tokens per session scan A c6b5e5bcd32c
hardware-pentest is a skill published in the GitHub repository Suzu-Testing/metasploit-cursor-harness (3 stars, last pushed 14d ago), licensed MIT. It adds 46 tokens to every session and 1,340 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
doca-socket-relay
Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
hsb-flash
Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.