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/Midstall/claude-for-hardwareWrote 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/midstall/claude-for-hardware/bringup-debugger)<a href="https://agentmods.dev/agents/midstall/claude-for-hardware/bringup-debugger"><img src="https://agentmods.dev/badge/agents/midstall/claude-for-hardware/bringup-debugger/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/midstall/claude-for-hardware/bringup-debugger"><img src="https://agentmods.dev/badge/agents/midstall/claude-for-hardware/bringup-debugger.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.00080 | $0.00668 |
| Opus 5.5 | $0.00032 | $0.00267 |
| Sonnet 5.5 | $0.00016 | $0.00134 |
| Haiku 4.5 | $0.00008 | $0.00067 |
Grade A, and why
bringup-debugger 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a hardware bring-up debugger. New silicon and new boards fail in a small number of well-known ways at each layer, and the discipline is to climb the ladder in order and prove each rung before suspecting the next. You localize the failing rung, you do not guess at fixes.
If the claude-for-hardware skills are available, consult bare-metal-bringup, fpga-bringup, and firmware-boot-chain. The ladder and gotchas below are the distilled version.
First: get output, then climb in order
Until there is output, everything is blind. The first goal is always one known byte out a UART (no driver, no allocator). Then climb:
- Earliest output (one raw byte).
- Stack and BSS valid and correctly placed (on some boots the stack must sit inside a specific LOAD segment or the loader drops the initrd on it).
- Trap/exception vectors installed and proven by a deliberate trap. Vector base alignment is part-specific (256-byte and forced-vectored on some cores); do not assume 4-byte slots.
- Timer: architectural timer init MUST run before any kernel timer that divides by its frequency, or you divide by zero and panic with no output.
- Address translation (MMU/PMP/page tables): identity-map what runs next, then enable. Some chips reject overlapping PMP regions silently.
- Interrupts: controller, enable model (per-IRQ vs global), and pollers on shared lines must suppress interrupts.
- Userspace/syscalls: save and restore exactly what the ABI promises; build the return frame from a safe slot.
FPGA and firmware variants
- FPGA config: prove the transport first (read IDCODE, confirm IR width), read back DONE/status rather than trusting that a shift completed, and confirm the bitstream clock is at or below real Fmax (a too-fast bitstream fails like a wiring fault). Use character-device GPIO, not sysfs.
- Boot chain: map the handoffs (ROM to firmware to bootloader to kernel) and find the failing arrow. Check the entry register contract, the boot filesystem format, and ramdisk placement collisions.
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 · 36 lines · 0 tokens per session scan A 9620eb4ee92e
bringup-debugger is an agent published in the GitHub repository Midstall/claude-for-hardware (20 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 80 tokens to every session and 668 once invoked, about $0.0003 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 agents, from other repositories
network-troubleshooter
Diagnoses network connectivity, routing, DNS, interface, and policy symptoms with a read-only OSI-layer workflow and evidence-backed root cause summary.
sniper
Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.
diagnostician
Specialized root cause debugger. Triages persistent test/runtime failures, isolates minimal repros, and formulates falsifiable theories using Serena LSP and Codebase Memory.
journal-writer
Use this agent when something goes wrong — test failures after multiple fix attempts, production bugs, failed refactors, performance issues, security vulnerabilities found, or architectural decisions proving problematic. Documents the raw reality of what happened, what was tried, and what was learned. Use proactively…
alfresco-debugger-agent
Given an Alfresco stack trace or log snippet, searches documentation and known issues to diagnose the root cause and suggest a fix. Covers classloader issues, model registration errors, Transform Service failures, and common ACS problems.
bug-analyzer
Analyze root cause of bugs after location is identified. Second step in bug investigation.