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 skills add telagod/code-abyss --skill designing-hardware-productsgit clone --depth 1 https://github.com/telagod/code-abyssWrote 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/telagod/code-abyss/designing-hardware-products)<a href="https://agentmods.dev/skills/telagod/code-abyss/designing-hardware-products"><img src="https://agentmods.dev/badge/skills/telagod/code-abyss/designing-hardware-products/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/telagod/code-abyss/designing-hardware-products"><img src="https://agentmods.dev/badge/skills/telagod/code-abyss/designing-hardware-products.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 73 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00058 | $0.00879 |
| Opus 5.5 | $0.00023 | $0.00352 |
| Sonnet 5.5 | $0.00012 | $0.00176 |
| Haiku 4.5 | $0.00006 | $0.00088 |
Grade A, and why
designing-hardware-products 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 1mo 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Designing Hardware Products
判断先于执行：决定「是否做 / 选什么 / 如何取舍」（栈、方案、架构、权衡）前，先读领域判断内核
skills/_kernel/hardware/SKILL.md——它管 judgment，本秘典管 execution；冲突时以内核判断为准。
From empty directory to shippable product. Requirements in, Gerber + .bin + .apk out.
When to use
| Scenario | Use | Why |
|---|---|---|
| New IoT / embedded product from scratch | Yes | Full pipeline |
| Adding BLE app to existing hardware | Partial | Phase 4 only |
| PCB redesign with existing firmware | Partial | Phase 3 only |
| One-off breadboard prototype | No | Overkill, just wire it |
Pipeline phases
Phase 1: System Design → DESIGN.md (architecture, topology, protocol)
Phase 2: Firmware → ESP-IDF components, FreeRTOS tasks, BLE GATT
Phase 3: Hardware → KiCad schematic → PCB → route → DRC → Gerber
Phase 4: Mobile App → UniApp (BLE, i18n, dev mode, SVG icons)
Phase 5: Verify + Package → build all → zip release
Each phase is independently re-runnable. Skip phases that already exist.
Key decision points
- MCU selection — ESP32-C3 (BLE+WiFi, RISC-V, cheap) vs ESP32-S3 (AI, USB) vs STM32 (low power) vs nRF (BLE-only)
- HV topology — if product needs high voltage (mosquito swatter, taser), see references/hv-design.md
- PCB form factor — match physical product shape, not default rectangle
- App framework — UniApp (WeChat+Android+iOS) vs React Native vs Flutter
Companion skills
- operating-kicad-eda — Phase 3 detail, KiCad MCP tool routing
- developing-software — firmware language patterns (C for ESP-IDF)
- developing-mobile-apps — app framework patterns
Usage
/designing-hardware-products "BLE mosquito swatter with kill counting, ESP32-C3, 30x100mm PCB strip"
References
| Topic | File |
|---|---|
| Phase execution details | pipeline-phases.md |
| KiCad 9 gotchas | kicad9-quirks.md |
| ESP-IDF patterns | esp-idf-patterns.md |
| HV circuit design | hv-design.md |
| UniApp patterns | uniapp-patterns.md |
What ships with it
5 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.
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.
- 1mo ago First seen · 75 lines · 58 tokens per session scan A ce9eaf89546e
designing-hardware-products is a skill published in the GitHub repository telagod/code-abyss (242 stars, last pushed 3mo ago), licensed MIT. It adds 58 tokens to every session and 879 once invoked, about $0.0002 per session on Opus 5.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
phone-control
Send commands to Android phones via ADB and iOS devices via Shortcuts/osascript automation.
hz-psdk-integration
Guides interactive Horizon Platform SDK (PSDK) integration for Meta VR and Horizon OS Android/Kotlin apps — analyzes the codebase, recommends public platform features, plans the integration, and validates on device. Use for workflow guidance; use hz-platform-sdk for the detailed API reference. Build paths: Standard…
hz-spatial-sdk
Builds spatial Android apps for Meta VR and Horizon OS with Meta Spatial SDK — ECS architecture, 2D panels, 3D objects, hybrid experiences. Use when creating Kotlin-based spatial applications. Build path: Meta Spatial SDK; use hz-quest-verify-first if the build path is unclear.
agent-device-lab
Prepare and check trusted macOS hosts for physical Android and iPhone tests with agent-device, ADB, and Xcode, or set up iPhone Mirroring separately.
portal
Build and sideload Android apps for Meta Portal devices (Portal, Portal+, Portal Mini, Portal Go, Portal TV) using metavr. Use when targeting Portal hardware — covers ADB enablement, the no-GMS constraint, manifest/launcher intent-filter requirements, icon density quirks (PNG-only, mipmap-xxxhdpi), the Smart Camera…
native-integration
Integrate native platform features via platform channels, native modules, or FFI. Use when accessing device hardware, OS APIs, or third-party native SDKs.