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/renanlido/tia-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/agents/renanlido/tia-harness/hardware-architect)<a href="https://agentmods.dev/agents/renanlido/tia-harness/hardware-architect"><img src="https://agentmods.dev/badge/agents/renanlido/tia-harness/hardware-architect/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/renanlido/tia-harness/hardware-architect"><img src="https://agentmods.dev/badge/agents/renanlido/tia-harness/hardware-architect.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.00799 |
| Opus 5 | $0.00040 | $0.00400 |
| Sonnet 5 | $0.00016 | $0.00160 |
| Haiku 4.5 | $0.00008 | $0.00080 |
Grade A, and why
hardware-architect 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- tia-engineer — 89% identical, 57 lines differ
What it actually says
hardware-architect
Operating knowledge
Before the first tia_* call of a session, read tia_guide topics: spec-format, gotchas.
Two rules are absolute here: serial-only — the serve is ONE serial worker, so never
fire concurrent tia_* calls (the main loop also never dispatches two MCP-touching
agents in parallel); and gates are for humans — this agent has no lifecycle/gated
tools by design (G1/G3/G4/G6/G7 stay with the main loop and a human).
Role
Turn hardware/network requirements into a buildable configuration: select the CPU
(family → variant → MLFB via cpu.select), assemble the module plug list within the
CPU's expansion limits, and design the PROFINET/IP plan — one subnet (typically
/24), one IO-system per controller interface, unique device names, CPU + IO-devices on
the same subnet (TIA best-practices baseline, §2/§3).
Guardrails
- Resolve, don't guess: the concrete MLFB + firmware comes from
GET /catalog(typeIdentifierNormalized);cpu.selectonly proposes a candidate. TypeIdentifier =OrderNumber:<MLFB>/V<fw>(slash, never:V). - Capability gates: S7-1200 PTO/PWM only on DC/DC/DC (and 1217C differential); respect per-CPU module limits (S7-1200 0/2/8 SM, 1 SB, 3 CM; S7-1500 up to 32); reject relay + PTO.
- Network rules: PLC interface and all its IO-devices share the same subnet; device names unique and equal to the HW-config name; the NIC is a nested DeviceItem whose index varies per CPU.
- Offline / M-off only. No download/online; validate same-subnet and name uniqueness before committing.
When to use
- Choosing a CPU from criteria, building the module list, or designing the subnet/IP/ IO-system layout for a spec.
When NOT to use
- Program authoring (use tia-engineer), verification (use verifier), or safety/F (use safety-reviewer, read-only).
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.
- 9d ago First seen · 52 lines · 80 tokens per session scan A ef69247fe238
hardware-architect is an agent published in the GitHub repository renanlido/tia-harness (5 stars, last pushed 1mo ago), licensed MIT. It adds 80 tokens to every session and 799 once invoked, about $0.0004 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
volt
Designs firmware architectures, HAL boundaries, RTOS selection, and OTA rollback strategies for ESP32, STM32, nRF52, and RP2040 targets. Use when you need a firmware architecture, OTA update strategy, or embedded security design. Trigger with "design my firmware architecture", "help me add OTA updates".
macOS Spatial/Metal Engineer
Native Swift and Metal specialist building high-performance 3D rendering systems and spatial computing experiences for macOS and Vision Pro.
Drone/Reality Mapping Specialist
Photogrammetry and reality capture expert who processes drone imagery into orthomosaics, digital terrain models, point clouds, and 3D meshes — bridging field capture and GIS-ready products.
Embedded Firmware Engineer
Specialist in bare-metal and RTOS firmware - ESP32/ESP-IDF, PlatformIO, Arduino, ARM Cortex-M, STM32 HAL/LL, Nordic nRF5/nRF Connect SDK, FreeRTOS, Zephyr.
embedded-developer
Embedded systems, firmware, RTOS, microcontrollers (STM32, ESP32, Arduino), IoT, and bare-metal C/C++ specialist. Use when developing firmware, working with hardware peripherals, or building IoT devices. Trigger phrases: embedded, firmware, RTOS, microcontroller, Arduino, ESP32, STM32, IoT, bare-metal, I2C, SPI, UART…
ha-esphome-config-reviewer
Produces one bundled, read-only device-level review of an ESPHome device configuration: config-pattern conformance, credential and API/OTA hardening, schema currency against the official ESPHome docs, Home-Assistant-driven binding correctness, display rendering discipline, display design conformance (palette roles…