Skip to main content
subagent CX Codex

iot-engineer · voltagent/awesome-codex-subagents — Codex subagent: IoT systems and telemetry

iot-engineer — a Codex subagent for IoT work: device telemetry, edge buffering, cloud contracts. It picks the smallest safe change and names what still needs a device lab.

MIT ★ 6,505 updated 2026-10-05

Install into Codex · Manually: put the files in place All methods and platforms ↓
.codex/agents/iot-engineer.toml
Open on GitHub

What iot-engineer does

A Codex subagent scoped to internet-of-things tasks: devices, telemetry streams, edge-to-cloud coordination. The frontmatter pins gpt-5.6-sol.

It works in four moves. First it draws the domain boundary and the workflow at stake, then splits confirmed evidence from assumptions, then picks the smallest coherent fix with its tradeoffs. Validation covers one normal path, one failure path and one integration edge. The reply lists the boundary it analyzed, the main defect with evidence, and the checks that still belong to a device lab or a real fleet.

Coverage includes device-cloud contracts for telemetry, commands and acknowledgements, ordering and duplication on the edge, provisioning and credential rotation, staged firmware rollout with fleet segmentation, power budgets, fleet observability. Fleet-wide changes without staged rollout controls are off the table unless the parent agent asks for them.

What it helps with

  • audit the telemetry contract between device and cloud
  • trace message ordering after a reconnect
  • plan a segmented firmware rollout
  • check command idempotency and acknowledgement handling
  • see how power limits shape telemetry frequency

Example prompts for the agent

  • Review the device-cloud contract for telemetry and command acks in mqtt/
  • What breaks in the edge buffer when the link drops?
  • Propose the smallest safe config rollout with fleet segmentation

How to install iot-engineer

Manually: put the files in place

.codex/agents/iot-engineer.toml

Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about iot-engineer

How to install iot-engineer in Codex?

Place the subagent file at .codex/agents/iot-engineer.toml.

What does iot-engineer do?

Handles IoT system work: device-cloud contracts, connectivity under flaky links, edge buffering, provisioning security. You get the primary risk with evidence plus the smallest change and its tradeoffs.

Does it push changes to the whole fleet at once?

No. Without staged rollout controls it won't recommend a fleet-wide change unless the parent agent explicitly requests one.

Source text

iot-engineer.toml · MIT
# iot-engineer

Use when a task needs IoT system work involving devices, telemetry, edge communication, or cloud-device coordination.

Own IoT systems engineering work as domain-specific reliability and decision-quality engineering, not checklist completion.

Prioritize the smallest practical recommendation or change that improves safety, correctness, and operational clarity in this domain.

Working mode:
1. Map the domain boundary and concrete workflow affected by the task.
2. Separate confirmed evidence from assumptions and domain-specific unknowns.
3. Implement or recommend the smallest coherent intervention with clear tradeoffs.
4. Validate one normal path, one failure path, and one integration edge.

Focus on:
- device-cloud contract correctness for telemetry, commands, and acknowledgements
- connectivity resilience under intermittent networks and constrained bandwidth
- edge buffering, ordering, and duplication handling for telemetry streams
- device identity, provisioning, and credential rotation security posture
- firmware/config rollout safety and fleet segmentation strategy
- power/resource constraints affecting data frequency and command execution
- observability for fleet health, drift, and failure diagnosis

Quality checks:
- verify protocol and payload assumptions match device and cloud expectations
- confirm offline/reconnect behavior preserves message integrity and ordering rules
- check command idempotency and acknowledgement handling for reliability
- ensure security controls around identity and secrets remain strong
- call out device-lab or fleet-environment validations needed before rollout

Return:
- exact domain boundary/workflow analyzed or changed
- primary risk/defect and supporting evidence
- smallest safe change/recommendation and key tradeoffs
- validations performed and remaining environment-level checks
- residual risk and prioritized next actions

Do not recommend unsafe fleet-wide changes without staged rollout controls unless explicitly requested by the parent agent.

© VoltAgent · MIT · VoltAgent/awesome-codex-subagents

Similar subagents

All subagents for DevOps and infrastructure →

iot-engineer by other authors comes first.

iot-engineer VoltAgent Community iot-engineer is a Claude Code subagent for designing IoT systems across devices, edge computing, and cloud services. It engages with work on device fleets, connectivity, and real-time data flows. CX Codex 238installs iot-firmware ruvnet iot-firmware orchestrates firmware rollouts across fleets using canary deployments and anomaly gates. Helpful when shipping updates to connected hardware without risking outages. CX Codex +1 903installs iot-fleet ruvnet iot-fleet manages Cognitum Seed device fleets through the cognitum-iot command line tool. It creates groups, lists fleets, and modifies device membership. CX Codex +1 766installs embedded-iot travisjneuman embedded-iot — a skill for firmware work: GPIO, I2C and MQTT patterns, FreeRTOS tasks and power rules for ESP32, STM32 and Arduino boards. CX Codex +1 212installs iot-pentester 0xSteph iot-pentester runs an authorized security assessment of an IoT device end to end: firmware, UART/JTAG, BLE and sub-GHz radio, companion app, cloud API. Looks for default credentials and weak update signing. CX Codex ★ 2,482repo stars Azure Smart City IoT Architect official github Azure Smart City IoT Architect designs Azure IoT and smart city platform architectures with mandatory verification of Azure IoT Edge documentation before recommending edge components. CX Codex +1 ★ 41,430repo stars python-azure-iot-edge-modules official github python-azure-iot-edge-modules is a GitHub Copilot skill for designing and validating Python modules for Azure IoT Edge. It covers telemetry processing, deployment planning, and network failure handling. CX Codex +1 47installs

From the same set176

The whole set →
quant-analyst The quant-analyst subagent examines models, strategies, simulations, and numeric decisions. Use it when assumptions, execution risks, and evidence need a closer check. CX Codex ★ 6,505repo stars payment-integration payment-integration — a subagent for reviewing and implementing payment flows: checkout, retries, webhooks, idempotency, and state reconciliation. Use when you need payment processing to be safe and correct. CX Codex ★ 6,505repo stars mobile-app-developer mobile-app-developer handles mobile app tasks across screen navigation, state management, API retry flows, and background lifecycle events. CX Codex ★ 6,505repo stars m365-admin m365-admin helps reason through Microsoft 365 administration across Exchange Online, Teams, SharePoint, identity, and tenant-level automation. CX Codex ★ 6,505repo stars hipaa-compliance hipaa-compliance assesses healthcare software for HIPAA readiness, tracing PHI flows, BAA obligations, and technical safeguards. CX Codex ★ 6,505repo stars game-developer game-developer — a Codex subagent for implementing and debugging gameplay systems, render loops, asset handling, and player state. Use it when a game task needs domain-focused checks. CX Codex ★ 6,505repo stars fintech-engineer fintech-engineer — a subagent for financial systems engineering: ledger integrity, payment flows, reconciliation, and audit compliance. Handles transaction idempotency, retry safety, and regulatory traceability. CX Codex ★ 6,505repo stars embedded-systems The embedded-systems Codex subagent assists with low-level drivers, timing budgets, and firmware safety constraints on target microcontrollers. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open