lean-iot
Skill2 starsChanged 56 days agoMITView on GitHub
Runs token-efficient defensive IoT and firmware-config reviews for Cursor and Codex. Inventories default passwords, telnet, open MQTT, and debug listeners in local device config, then reports compact hardening fixes. Use when the user asks for IoT security, firmware config, MQTT, default credentials, or embedded debug ports. Do not use for device exploits, UART attacks, or unauthorized firmware dumps.
In this repository21 other files it gives its agents.
- lean-cryptoSkill
- lean-mobileSkill
- lean-privacySkill
- lean-secSkill
- lean-webSkill
- lean-a11ySkill
- lean-depsSkill
- lean-docsSkill
- lean-perfSkill
- lean-reviewSkill
- lean-ciSkill
- lean-cloudSkill
- lean-costSkill
- lean-hardeningSkill
- lean-netSkill
- lean-dfirSkill
- lean-ir-playbookSkill
- lean-malwareSkill
- lean-osintSkill
- lean-phishSkill
- lean-threat-modelSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 38
Run device. Queue admin/admin, telnet, MQTT without auth, serial debug, 0.0.0.0 management ports.
- Distinctive: line 45
No UART/JTAG attack steps, no firmware unpack recipes.
- Very specific: line 46
Default passwords: report the kind, not a live unique password if present ([REDACTED]).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Lean IoT
Defensive review of device config the user already has. Scripts list default secrets and debug listeners; you do not flash or attack devices.
Let SKILL_ROOT be the folder that contains this SKILL.md. Prefer python3; on Windows use py -3.
python3 "$SKILL_ROOT/scripts/lean_iot.py" device .
python3 "$SKILL_ROOT/scripts/lean_iot.py" trim --chars 2500 path/to/out.txtMode
Default lean.
| Mode | Budget |
lean | device + up to 8 slices; references/defaults.md; ≤6 findings |
standard | up to 16 slices; ≤10 findings |
deep | needed refs only; ≤16 findings |
Workflow
- Run
device. Queueadmin/admin, telnet, MQTT without auth, serial debug,0.0.0.0management ports. - Slice-read the matching conf. Cap quotes at 12 lines.
- Report disable-debug / unique password / TLS MQTT. Stop unless asked to patch.
Hard rules
- Config in this workspace only. No scanning random cameras or shodan.
- No UART/JTAG attack steps, no firmware unpack recipes.
- Default passwords: report the kind, not a live unique password if present (
[REDACTED]).
Report template
## Lean-iot (`<mode>`)
**Device/tree:** <folder> | **Budget:** files_read=<n>
| Sev | Location | Issue | Fix |
|-----|----------|-------|-----|
| HIGH | file:line | telnet enabled | disable; SSH with keys |Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.