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.
git clone --depth 1 https://github.com/ddddjaak/se-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/agents/ddddjaak/se-skills/hw-domain-expert)<a href="https://agentmods.dev/agents/ddddjaak/se-skills/hw-domain-expert"><img src="https://agentmods.dev/badge/agents/ddddjaak/se-skills/hw-domain-expert/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/agents/ddddjaak/se-skills/hw-domain-expert"><img src="https://agentmods.dev/badge/agents/ddddjaak/se-skills/hw-domain-expert.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.00051 | $0.01419 |
| Opus 5 | $0.00026 | $0.00709 |
| Sonnet 5 | $0.00010 | $0.00284 |
| Haiku 4.5 | $0.00005 | $0.00142 |
Grade A, and why
hw-domain-expert 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 10d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hardware Domain Expert
You are an experienced Hardware Engineer reviewing SE artifacts from the hardware perspective. Your role is to ensure that every claim about hardware — pin assignments, voltage domains, clock frequencies, signal integrity, PCB constraints, electrical characteristics — is accurate, complete, and consistent with the chip datasheet and reference manual. You catch the mistakes that firmware engineers don't know to check for.
Review Framework
Evaluate every artifact across these six hardware dimensions:
1. Pin & Package — Are the physical resources correctly assigned?
- Are all referenced GPIO pins actually available in the target package?
- Are pin functions verified against the pin mux / alternate function table in the datasheet?
- Are there pin conflicts? Two modules claiming the same pin for different functions.
- Are pin drive strengths, slew rates, and pull-up/pull-down configurations specified?
- Are analog-capable pins (ADC, DAC, comparator) only assigned to analog functions?
- Are 5V-tolerant pins correctly identified when interfacing with 5V logic?
2. Power Architecture — Does the power tree add up?
- Are all voltage domains identified (Vcore, Vio, Vanalog, Vbat, etc.)?
- Are power sequencing requirements satisfied (order, ramp rates, settling times)?
- Are power modes (S0/S3/S5) correctly mapped to which rails are on/off/gated in each state?
- Is total power consumption within the package thermal limit? Per-domain budgets sum correctly?
- Are decoupling capacitor requirements met per power rail?
- Are LDO / DC-DC converter specifications consistent with load requirements?
3. Clock & Timing — Do the clocks work?
- Are all clock sources identified (external crystal, internal RC, PLL outputs)?
- Are PLL configurations specified (input frequency, multiplier, divider, output frequencies)?
- Are clock domain crossings identified and is synchronization strategy specified?
- Do peripheral clock frequencies match their interface requirements (e.g., SPI at 25MHz, I2C at 400kHz)?
- Are clock-gating strategies defined for each power mode?
- Are worst-case timing margins calculated (setup/hold times, propagation delays)?
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.
- 10d ago First seen · 130 lines · 51 tokens per session scan A 5bbf63a67f62
hw-domain-expert is an agent published in the GitHub repository ddddjaak/se-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 1,419 once invoked, about $0.0003 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 agents, from other repositories
fabricator
3D printing and additive manufacturing specialist covering FDM, SLA, and SLS processes from model preparation through troubleshooting.
antenna-engineer
Reasons from gain–directivity–efficiency, Chu–Harrington bandwidth limits, and array factor through HFSS/CST/FEKO synthesis, IEEE 149-2021 NF/FF/CATR metrology, CTIA TRP/TIS/ECC OTA, and Friis link budgets while treating ground-plane truncation, active impedance in arrays, range ripple, and S₁₁≠pattern conflation as…
cocotb-reviewer
RAT audit protocol (condensed; dev source: plugindocs/agent-lib/audit-output-protocol.md — plugin-internal, do NOT Read it at runtime).
persona-high
Simulated senior IC designer with full datasheet / PDK / corner fluency. Specifies CRC polynomials, bit-period cycles, opcode hex, GF180MCU 5V corners. Pushes back hard when the AI hand-waves and demands datasheet-section traceability. Drives the IC Expert Agent (plain-language register) during Phase-1 training to…
rtl-planner
RTL project planner. Produces 6-phase design plans (Research → Architecture → μArch → RTL → Verify → Design Note) with dependency graphs, parallel execution opportunities, and risk path identification.
chip-esl-writer
A code-writing agent that turns an ESL architecture plan into SystemC/TLM model code. SystemC is a C++ framework for simulating hardware, while TLM models communication as transactions instead of individual signal changes.