Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
/plugin marketplace add iot-forge/m5stack-skillsnpx agentmods add plugins/iot-forge/m5stack-skills/marketplacegit clone --depth 1 https://github.com/iot-forge/m5stack-skillsGrade A, and why
m5stack 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 2d 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.
What it actually says
{
"name": "m5stack",
"owner": {
"name": "IoT Forge",
"url": "https://github.com/iot-forge"
},
"metadata": {
"description": "Hardware reference and firmware-development skills for M5Stack Controllers and the Espressif SoCs they're built on.",
"version": "0.1.0"
},
"plugins": [
{
"name": "cardputer",
"source": "./plugins/cardputer",
"description": "M5Stack Cardputer family hardware reference \u2014 pinout, peripherals, and Arduino/PlatformIO/ESP-IDF/UIFlow2 setup. Covers Cardputer Adv and the Cap LoRa-1262 (SX1262 + ATGM336H GNSS) accessory.",
"category": "hardware",
"keywords": [
"m5stack",
"cardputer",
"cap-lora-1262",
"sx1262",
"lora",
"esp32-s3",
"firmware",
"embedded"
]
},
{
"name": "core",
"source": "./plugins/core",
"description": "M5Stack Core-family Controller hardware references \u2014 Core2 (incl. Core2 For AWS) and Tab5.",
"category": "hardware",
"keywords": [
"m5stack",
"core2",
"tab5",
"esp32",
"esp32-p4",
"firmware",
"embedded"
]
},
{
"name": "esp32-chips",
"source": "./plugins/esp32-chips",
"description": "Chip-level ESP-IDF capability references for the Espressif SoCs M5Stack boards are built on: classic ESP32, ESP32-S3, ESP32-C6, ESP32-P4. Board skills point into these for peripheral, sleep, memory, and radio depth.",
"category": "hardware",
"keywords": [
"esp32",
"esp32-s3",
"esp32-c6",
"esp32-p4",
"esp-idf",
"risc-v",
"xtensa",
"embedded"
]
}
]
}
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.
- 2d ago First seen · 61 lines scan A 316be9f63c1d
m5stack is a plugin published in the GitHub repository iot-forge/m5stack-skills (2 stars, last pushed 7d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
reterminal-sticky
Claude Code plugins for the Seeed Studio reTerminal Sticky e-ink device.
sticky-device
Hardware, firmware, and publishing context for the Seeed Studio reTerminal Sticky (ESP32-S3 e-ink device).
embedded-agent-skills
Agent Skills for embedded systems development including GPIO configuration, pin validation, and hardware initialization code generation.
gpio-config
GPIO pin assignment, validation, and code generation for Raspberry Pi and ESP32 embedded projects. Supports I2C, SPI, UART, PWM, 1-Wire, CAN, ADC protocols with 28 device profiles and hardware safety warnings.
jlink-mcp
Plugin marketplace listing 1 plugin: jlink-mcp.
membrowse
MemBrowse memory tracking integration for embedded firmware projects. Automatically sets up GitHub workflows for RAM/Flash analysis.