Borrowing it
Nothing to install: this file belongs to SensorsIot/Embedded-AI-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/SensorsIot/Embedded-AI-Harness/main/.claude/skills/define/SKILL.mdgit clone --depth 1 https://github.com/SensorsIot/Embedded-AI-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/sensorsiot/embedded-ai-harness/define)<a href="https://agentmods.dev/skills/sensorsiot/embedded-ai-harness/define"><img src="https://agentmods.dev/badge/skills/sensorsiot/embedded-ai-harness/define.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00159 | $0.04338 |
| Opus 5 | $0.00079 | $0.02169 |
| Sonnet 5 | $0.00032 | $0.00868 |
| Haiku 4.5 | $0.00016 | $0.00434 |
Grade A, and why
define 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 — 367 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Define — Phase 0 (FSD skill)
Creates and maintains the WHAT: what the system must do, stated so that compliance can be demonstrated. Every approved Must/Should carries a verification contract — the requirement and its proof are co-engineered, because attempting the contract is the quality gate: a requirement whose stimulus cannot be stated is not finished.
Interface with the loop: contracts flow down — /build consumes them,
never edits them. Spec-defect findings flow up — when a declaration or an
executable test proves a contract unsatisfiable, /build reports and this
skill amends. A change request's Definition delta lands here
(/build → ../build/references/change-request.md).
0. Scope — what this skill does and does not do
Three things it must never do: claim a requirement is verified because code or a test merely exists; turn a recommendation into an approved requirement silently; invent a normative threshold, tolerance, security assumption, or failure behaviour.
| Activity | This skill | /build (Method) |
Dev skills | Testbench skills |
|---|---|---|---|---|
| Define scope, requirements, states, interfaces | Yes | No | No | No |
| Write verification contracts | Yes | Consumes | No | No |
| Architecture decisions | Yes (records) | No | May propose | No |
| Design and declare tests, own the plan | No | Yes | No | No |
| Generate firmware and executable tests | No | Dispatches | Yes | Support |
| Execute tests, capture evidence | No | Sequences | Processes | Captures |
| Decide unresolved product questions | No | No | No | No |
GitHub is the system of record. The FSD, the plan, tests, and evidence are
version-controlled artefacts; chat history is not authoritative. If the
project has no repository, create it as the first act — git init, the §10
skeleton, an initial commit — and commit each artefact as it is finished. An
untracked Method plane is unshared and therefore undocumented.
1. Scale and reach
Depth scales to inferred complexity. The core is domain-neutral — embedded, networking, SDR, IoT, cloud, mobile, hybrid — with optional packs (§14).
What ships with it
16 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/authoring.md 14 KB
- references/canonical-fsd-structure.md 14 KB
- references/complexity-scaling.md 4.0 KB
- references/domains/esp32.md 13 KB
- references/evolve-mode.md 2.4 KB
- references/example-output.md 6.1 KB
- references/finalisation.md 4.2 KB
- references/requirement-quality.md 10 KB
- references/system-models.md 6.0 KB
- references/templates/00-Overview.md 3.3 KB
- references/templates/method/AI-Workflow.md 2.5 KB
- references/templates/method/README.md 877 B
- references/templates/method/standards/engineering.md 1.4 KB
- references/templates/method/standards/testing.md 4.9 KB
- references/templates/user-documentation/User-Manual.md 2.7 KB
- references/three-planes.md 6.4 KB
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 · 367 lines · 159 tokens per session scan A 0d8c4d4ae704
define is a skill published in the GitHub repository SensorsIot/Embedded-AI-Harness (173 stars, last pushed 28d ago), licensed MIT. It adds 159 tokens to every session and 4,338 once invoked, about $0.0008 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-30.
Other skills, from other repositories
m5stack-cap-lora-1262
Hardware reference and firmware helper for the M5Stack Cap LoRa-1262 (SKU U214) — a snap-on cap for the Cardputer Adv (K132-Adv) and CardputerZero that carries a Semtech SX1262 sub-GHz LoRa radio (868–923 MHz, +22 dBm TX, external RP-SMA antenna) and an ATGM336H-6N GNSS receiver (GPS/QZSS/BeiDou/Galileo/GLONASS, UART…
new-device-skill
Build or update an M5Stack hardware skill in this marketplace — a Controller (a board that runs firmware, like Core2 or AtomS3), a Unit (a peripheral you drive from a Controller, like a ToF sensor or a relay), or a Chip (an Espressif SoC capability layer, like esp32-c6). Use whenever adding a new board/unit/chip to…
m5stack-tab5
Hardware reference and development helper for the M5Stack Tab5 (product code C145) — an ESP32-P4-based 5" touchscreen IoT/industrial terminal with an ESP32-C6 wireless co-processor, MIPI-DSI display, MIPI-CSI camera, ES8388 audio codec, BMI270 IMU, RX8130CE RTC, RS485, and a removable NP-F550 battery. Use this skill…
m5stack-core2
Hardware reference and development helper for the M5Stack Core2 family — a 2.0" touchscreen ESP32 (classic, Xtensa LX6) Controller built around an AXP192 power management IC, ILI9342C display, FT6336U capacitive touch, BM8563 RTC, and (on original/1.1/1.3 revisions) an MPU6886 or BMI270 IMU. Covers the plain Core2…
esp32-c6
Chip-level ESP-IDF capability reference for the ESP32-C6 SoC (single-core RISC-V HP core + RISC-V LP core, WiFi 6 + BLE 5.3 + Thread/Zigbee) — what the chip can do, distinct from any board's wiring. Use when a user wants to exploit ESP32-C6 hardware — WiFi 6/BLE/802.15.4 radio coexistence (Thread Border Router, Zigbee…
esp32
Chip-level ESP-IDF capability reference for the classic ESP32 SoC (dual-core Xtensa LX6) — what the chip can do, distinct from board wiring. Covers the ESP32-D0WDQ6-V3 / ESP32-D0WD-V3 / ESP32-D0WDR2-V3 die family used in ESP32-WROOM-32 and ESP32-WROVER modules. Use for RMT (IR/WS2812), LEDC (PWM), I2S (audio/parallel…