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.
npx agentmods add instructions/iot-forge/m5stack-skills/claude-mdgit clone --depth 1 https://github.com/iot-forge/m5stack-skillsWrote 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/instructions/iot-forge/m5stack-skills/claude-md)<a href="https://agentmods.dev/instructions/iot-forge/m5stack-skills/claude-md"><img src="https://agentmods.dev/badge/instructions/iot-forge/m5stack-skills/claude-md.svg" alt="Measured on agentmods" 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 | $0.00521 | $0.00521 |
| Opus 5 | $0.00260 | $0.00260 |
| Sonnet 5 | $0.00104 | $0.00104 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
m5stack-skills CLAUDE.md 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 3d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working in this repo
This is a Claude Code plugin marketplace distributing hardware-reference
skills for M5Stack firmware development. Marketplace name: m5stack.
Published from github.com/iot-forge/m5stack-skills.
Layout
.claude-plugin/marketplace.json the catalog users install from
plugins/<plugin>/ a shipped plugin
.claude-plugin/plugin.json its manifest
skills/<slug>/SKILL.md a shipped skill
skills/<slug>/references/*.md loaded on demand, not up front
docs/catalog/*.md the work queue — what's built, what's next
docs/notes/<slug>.md per-skill build metadata (sourcing, confidence)
scripts/validate.py structural checks; CI runs this
docs/ never ships to users — it's for whoever maintains this repo.
Two rules that fail silently
Bump the plugin version. Claude Code pins each plugin to the version
in its plugin.json. Change a skill's content without bumping it and
existing users keep their cached copy — no error, no warning, and no signal
that your correction never landed. Any change under plugins/<name>/ needs
a bump to plugins/<name>/.claude-plugin/plugin.json.
Validate before pushing.
python3 scripts/validate.py
python3 scripts/check_version_bump.py origin/main # on a branch
Building or updating a skill
Use the new-device-skill skill in .claude/skills/ — it carries the
research workflow, the Controller/Unit/Chip distinction, the file-layout
convention, and the specific failure modes this project has already hit.
Read it before adding a board; the conventions are load-bearing, not
stylistic.
Start from docs/catalog/controllers.md (or units.md / chips.md) to
pick what to build next, and update that row when you finish.
Writing style for skills
These are read by a model that is about to write firmware, not by a human browsing docs. Lead with what most often goes wrong. State I2C addresses and GPIO numbers exactly. Mark anything sourced from a forum post or third-party teardown as such, inline — a reader needs to know which claims are load-bearing on one unverified source. Never smooth over a gap; say it's unverified and point at the schematic.
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.
- 3d ago First seen · 56 lines · 521 tokens per session scan A 555ac6f811f9
m5stack-skills CLAUDE.md is an instructions file published in the GitHub repository iot-forge/m5stack-skills (2 stars, last pushed 8d ago), licensed MIT. It adds 521 tokens to every session, about $0.0026 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 instructions, from other repositories
ws-ESP32-S3-CAM CLAUDE.md
Instructions for chayuto/ws-ESP32-S3-CAM, covering claude.md — ws-esp32-s3-cam, publish boundary — read this before committing, repo layout, board facts (verified on this unit) and key differences from sibling c6 repos.
FastLED GEMINI.md
Gemini CLI instructions for FastLED/FastLED, a project described as: The FastLED library for colored LED animation on Arduino. Please direct questions/requests for help to the FastLED Reddit community: http://fastled.io/r We'd like to use github "issues" just for tracking library bugs / enhancements.
p3a AGENTS.md
AGENTS.md instructions for fabkury/p3a: You are a highly proficient embedded systems developer with expertise in ESP-IDF and ESP32-P4. The project is p3a, a Wi-Fi pixel art player. When using idf.py, activate the ESP-IDF v5.5.4 environment with . C:\Espressif\tools\Microsoft.v5.5.4.PowerShellprofile.ps1, then set…
esp32-docs-mcp CLAUDE.md
Claude Code instructions for ozonejunkieau/esp32-docs-mcp, covering claude.md — operating guide, hard rules, environment traps, commands and current state.
NucleoOs CLAUDE.md
Claude Code instructions for indecenti/NucleoOs, covering nucleoos — working notes for claude, hard constraints — design for the worst case, repository layout, default dev loop — host first, flash last and build / release — via ota + web api, not serial.
xiaozhi-esp32 AGENTS.md
AGENTS.md instructions for 78/xiaozhi-esp32, covering agents.md, project, architecture, required rules and boards and configuration.