Skip to content
Agentmart
Submit a tool

iot-testing

Use when the user asks to analyze firmware, embedded devices, protocol handlers, hardcoded secrets, or memory corruption risk in IoT targets.

Skill by pentrestion

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/pentrestion-iot-testing

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use when the user asks to analyze firmware, embedded devices, protocol handlers, hardcoded secrets, or memory corruption risk in IoT targets.

Use cases: testing, security

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/iot-testing

What's inside

Skill name
iot-testing
Description
Use when the user asks to analyze firmware, embedded devices, protocol handlers, hardcoded secrets, or memory corruption risk in IoT targets.
License
MIT
Instructions
20 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# IoT Testing

This skill addresses firmware extraction, embedded protocol analysis, and emulated validation for IoT and embedded products.

## Scope
- Validate the firmware hash and target architecture.
- Treat the environment as untrusted and isolated.
- Use emulation-first methods before any live hardware validation.

## Techniques
- Firmware extraction and filesystem analysis
- Protocol parser testing and mutation
- Static analysis for hardcoded secrets and unsafe sinks
- Emulator-based behavior validation

## Safety
- Network must remain disabled unless explicitly approved.
- Physical-device testing requires separate authorization.

From pentrestion/AI-Security-Workflow, MIT.

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Oct 22, 2026 (6 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from pentrestion

Cite this page

iot-testing skill. Agent Mart. https://agentmart.dev/skills/pentrestion-iot-testing (last updated 2026-10-24)