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 P47Phoenix/Claude-Plugins --skill hardware-flowgit clone --depth 1 https://github.com/P47Phoenix/Claude-PluginsWrote 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/p47phoenix/claude-plugins/hardware-flow)<a href="https://agentmods.dev/skills/p47phoenix/claude-plugins/hardware-flow"><img src="https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/hardware-flow/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/p47phoenix/claude-plugins/hardware-flow"><img src="https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/hardware-flow.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00116 | $0.11364 |
| Opus 5.5 | $0.00046 | $0.04546 |
| Sonnet 5.5 | $0.00023 | $0.02273 |
| Haiku 4.5 | $0.00012 | $0.01136 |
Grade A, and why
hardware-flow 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 — 1,024 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hardware Flow -- Pipeline Orchestrator
Design Principle: Hardware Team Delivery with Validation Gates and Physical-World Integration
This skill is the ORCHESTRATOR. It coordinates the hardware delivery team through a structured 8-stage pipeline but NEVER produces domain artifacts directly. All domain work -- requirements, schematics, layout reviews, DFM reports, compliance packages, test procedures -- is delegated to worker skills that operate as sub-agents with isolated context.
Disclaimer -- AI Scope Limitations: This pipeline coordinates AI-assisted design review and documentation. It does NOT replace physical testing, lab measurements, certified compliance testing, or professional engineering sign-off. Human-execution stages (Prototype, Pilot Run, Production Release) require physical work that AI cannot perform. All compliance outputs are pre-compliance assessments only -- formal certification requires accredited test labs.
Core Principles
-
Delegation, not execution (Prime Directive). The orchestrator manages flow, routing, and validation. Worker skills (hw-product-owner, electrical-engineer, pcb-layout-engineer, manufacturing-engineer, compliance-engineer, test-engineer) produce ALL domain artifacts. Workers are invoked as sub-agents using the Agent tool.
The orchestrator NEVER writes domain content. This is non-negotiable. Explicit anti-patterns (any of these is a Prime Directive violation):
- Writing a requirements doc, schematic review, DFM report, compliance analysis, or test procedure with Write or Edit because "it's simple"
- Drafting a short artifact inline and saving it to skip an Agent dispatch
- Writing a compound prompt that asks one sub-agent to act as multiple roles (see "One Role = One Sub-Agent" below)
- Collapsing two review passes into one by pasting prior findings into the next reviewer's prompt
- Forwarding artifact content (not paths) between sub-agents through the orchestrator
What ships with it
15 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/aliases/engineering.yml 4.3 KB
- references/bom-gate.md 8.6 KB
- references/compliance-gate.md 11 KB
- references/config-schema.md 9.0 KB
- references/dfm-gate.md 9.5 KB
- references/kicad-integration.md 12 KB
- references/memory-protocol.md 11 KB
- references/pipeline-stages.md 23 KB
- references/project-types.md 8.6 KB
- references/quality-gates.md 34 KB
- references/rework-loops.md 10.0 KB
- references/schematic-review-gate.md 19 KB
- references/setup-wizard.md 9.1 KB
- references/state-management.md 12 KB
- references/team-patterns.md 14 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.
- 1mo ago First seen · 1,024 lines · 116 tokens per session scan A ff3acb204029
hardware-flow is a skill published in the GitHub repository P47Phoenix/Claude-Plugins (2 stars, last pushed 2d ago), licensed MIT. It adds 116 tokens to every session and 11,364 once invoked, about $0.0005 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-31.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
holoscan-install-wheel
Install Holoscan SDK 5.x CUDA 13 Python wheels in an isolated environment, choosing the full stack or version-matched components.
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
doca-socket-relay
Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…
hsb-flash
Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must…