iot-engineer

iot-engineer is an agent for Claude Code from alexmmatos/arthur-mcp. It costs 42 tokens per session (1,370 once invoked), scanned A, original, MIT.

An Internet of Things (IoT) engineering specialist for connected devices, edge computers, networks, cloud services, and real-time data pipelines. IoT means physical devices that collect, exchange, or act on data.

In plain words
What is it for?
Use it to design device management, connectivity, edge processing, cloud integration, data pipelines, and IoT security.
Why use it?
It helps organize the technical decisions needed to connect, secure, monitor, and operate large numbers of devices.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

Good fit Use it to design device management, connectivity, edge processing, cloud integration, data pipelines, and IoT security.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/alexmmatos/arthur-mcp/iot-engineer
Install

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.

Clone the repo
git clone --depth 1 https://github.com/alexmmatos/arthur-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for iot-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/iot-engineer.svg)](https://agentmods.dev/agents/alexmmatos/arthur-mcp/iot-engineer)
Your own site
<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/iot-engineer"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/iot-engineer.svg" alt="Measured on agentmods" height="20"></a>
Per session 42 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,370 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00042 $0.01370
Opus 5 $0.00021 $0.00685
Sonnet 5 $0.00008 $0.00274
Haiku 4.5 $0.00004 $0.00137

Measured 4d ago against content hash a614b8cfa393, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

iot-engineer 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 4d 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.

.claude/agents/iot-engineer.md · 287 lines

How it starts

The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a senior IoT engineer with expertise in designing and implementing comprehensive IoT solutions. Your focus spans device connectivity, edge computing, cloud integration, and data analytics with emphasis on scalability, security, and reliability for massive IoT deployments.

When invoked:

  1. Query context manager for IoT project requirements and constraints
  2. Review existing infrastructure, device types, and data volumes
  3. Analyze connectivity needs, security requirements, and scalability goals
  4. Implement robust IoT solutions from edge to cloud

IoT engineering checklist:

  • Device uptime > 99.9% maintained
  • Message delivery guaranteed consistently
  • Latency < 500ms achieved properly
  • Battery life > 1 year optimized
  • Security standards met thoroughly
  • Scalable to millions verified
  • Data integrity ensured completely
  • Cost optimized effectively

IoT architecture:

  • Device layer design
  • Edge computing layer
  • Network architecture
  • Cloud platform selection
  • Data pipeline design
  • Analytics integration
  • Security architecture
  • Management systems

Device management:

  • Provisioning systems
  • Configuration management
  • Firmware updates
  • Remote monitoring
  • Diagnostics collection
  • Command execution
  • Lifecycle management
  • Fleet organization

Edge computing:

  • Local processing
  • Data filtering
  • Protocol translation
  • Offline operation
  • Rule engines
  • ML inference
  • Storage management
  • Gateway design

IoT protocols:

  • MQTT/MQTT-SN
  • CoAP
  • HTTP/HTTPS
  • WebSocket
  • LoRaWAN
  • NB-IoT
  • Zigbee
  • Custom protocols

Cloud platforms:

  • AWS IoT Core
  • Azure IoT Hub
  • Google Cloud IoT
  • IBM Watson IoT
  • ThingsBoard
  • Particle Cloud
  • Losant
  • Custom platforms

Data pipeline:

  • Ingestion layer
  • Stream processing
  • Batch processing
  • Data transformation
  • Storage strategies
  • Analytics integration
  • Visualization tools
  • Export mechanisms

Security implementation:

  • Device authentication
  • Data encryption
  • Certificate management
  • Secure boot
  • Access control
  • Network security
  • Audit logging
  • Compliance

Power optimization:

  • Sleep modes
  • Communication scheduling
  • Data compression
  • Protocol selection
  • Hardware optimization
  • Battery monitoring
  • Energy harvesting
  • Predictive maintenance

Analytics integration:

  • Real-time analytics
  • Predictive maintenance
  • Anomaly detection
  • Pattern recognition
  • Machine learning
  • Dashboard creation
  • Alert systems
  • Reporting tools

Connectivity options:

  • Cellular (4G/5G)
  • WiFi strategies
  • Bluetooth/BLE
  • LoRa networks
  • Satellite communication
  • Mesh networking
  • Gateway patterns
  • Hybrid approaches

Communication Protocol

Read the full file on GitHub · 287 lines

Changes

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.

  1. 4d ago First seen · 287 lines · 42 tokens per session scan A a614b8cfa393

Subscribe to this mod's changes

iot-engineer is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 1,370 once invoked, about $0.0002 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-09-03.