iot-simulator

iot-simulator is a skill for Claude Code, Codex from jonmikeli/ai-iot-tools-and-resources. It costs 91 tokens per session (1,333 once invoked), scanned A, original, MIT.

A tool for creating virtual Internet of Things devices that communicate with Azure IoT Hub. IoT devices are connected hardware such as sensors or machines; Azure IoT Hub is Microsoft’s service for connecting and managing them.

In plain words
What is it for?
Use it to provision simulated devices through Azure DPS, send telemetry, receive commands or messages, update device settings, test device twins, and run device-fleet scenarios.
Why use it?
It lets developers test device registration, messages, telemetry, commands, and settings without needing physical devices, including tests involving large groups of devices.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to provision simulated devices through Azure DPS, send telemetry, receive commands or messages, update device settings, test device twins, and run device-fleet scenarios.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jonmikeli/ai-iot-tools-and-resources/iot-simulator
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.

Any agent
npx skills add jonmikeli/ai-iot-tools-and-resources --skill iot-simulator
Clone the repo
git clone --depth 1 https://github.com/jonmikeli/ai-iot-tools-and-resources

Made for: Claude Code, Codex.

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-simulator

README.md
[![agentmods](https://agentmods.dev/badge/skills/jonmikeli/ai-iot-tools-and-resources/iot-simulator/github.svg)](https://agentmods.dev/skills/jonmikeli/ai-iot-tools-and-resources/iot-simulator)
Your own site
<a href="https://agentmods.dev/skills/jonmikeli/ai-iot-tools-and-resources/iot-simulator"><img src="https://agentmods.dev/badge/skills/jonmikeli/ai-iot-tools-and-resources/iot-simulator/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.

agentmods 80×15 button for iot-simulator

Your own site · 80×15
<a href="https://agentmods.dev/skills/jonmikeli/ai-iot-tools-and-resources/iot-simulator"><img src="https://agentmods.dev/badge/skills/jonmikeli/ai-iot-tools-and-resources/iot-simulator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 91 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,333 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.00091 $0.01333
Opus 5 $0.00046 $0.00666
Sonnet 5 $0.00018 $0.00267
Haiku 4.5 $0.00009 $0.00133

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

Security

Grade A, and why

iot-simulator 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.

plugins/copilot/iot-developer-plugin/skills/iot-simulator/SKILL.md · 97 lines

How it starts

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

IoT Simulator Skill

Simulate IoT devices and interactions with Azure IoT Hub. This skill allows you to create virtual devices that can provision with Azure IoTHub Device Provisioning Service (DPS) using enrollment groups, send telemetry, receive commands, receive messages, receive C2D desired properties, and update their device twin. IoT devices can be simulated alone or in large fleets. Use this skill for testing IoT solutions without needing physical hardware.


Table of Contents

  1. General Principles
  2. Start/Stop Simulated Devices
  3. Provisioning Simulated Devices with DPS Enrollment Groups
  4. Running Devices
  5. Underlying Technical Aspects
  6. Error Handling & Retry Guidance

1. General Principles

  • IoT Simulator MCP Server For IoT Device simulation features, always use tools from the IoT Simulator MCP Server.
  • Confirm destructive operations (disable) with the user before executing, unless the user has already confirmed in their message.
  • Scope awareness: Ask the user for the IoT Hub name / connection scope if it is not already established in the conversation or pre-configured in the MCP server.
  • System: IoT device simulators run as Docker containers. DO NOT SHOW this to users.
  • System Integrity: Every time a simulator is stopped, the related and underlying container is meant to be destroyed. Check this consistency if the user requests to clean up.
  • Present results clearly: Format device lists as tables with columns deviceId | status | lastActivityTime.
  • Hosting: devices can be simulated in one single container or one simulator per container. Clarify the user's intent and constraints before starting many devices at once.
    • Single container: device IDs are auto-generated based on a naming pattern; specific IDs cannot be assigned.
    • Multiple containers (one per device): specific device IDs can be assigned.
  • Secrets management: if tools create secrets, never show them to users in clear unless EXPLICITLY requested by the user.

Read the full file on GitHub · 97 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. 10d ago First seen · 97 lines · 91 tokens per session scan A ec9cdc1c1907

Subscribe to this mod's changes

iot-simulator is a skill published in the GitHub repository jonmikeli/ai-iot-tools-and-resources (1 stars, last pushed 3mo ago), licensed MIT. It adds 91 tokens to every session and 1,333 once invoked, about $0.0005 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.

Related

Other skills, from other repositories

analyze-tensegrity-system

Analyze a tensegrity system by identifying compression struts and tension cables, classifying type (class 1/2, biological/architectural), computing prestress equilibrium, verifying stability via Maxwell's rigidity criterion, and mapping biological tensegrity (microtubules, actin, intermediate filaments). Use when…

pjt222/agent-almanac · 94 tokens

design-electromagnetic-device

Design practical electromagnetic devices including electromagnets, DC and brushless motors, generators, and transformers by bridging theory to application. Use when sizing a solenoid or toroidal electromagnet for a target field or force, selecting motor topology and computing torque and efficiency, designing a…

pjt222/agent-almanac · 86 tokens

analyze-kernel-bottleneck

Systematically identify whether a GPU kernel is compute-bound, memory-bound, or latency-bound using roofline analysis, occupancy calculations, compute/load ratio per tile, and SASS instruction inspection. Produces a decision matrix for optimization strategy selection (cp.async, warp interleaving, tiling…

pjt222/agent-almanac · 77 tokens

analyze-magnetic-field

Calculate and visualize magnetic fields produced by current distributions using the Biot-Savart law, Ampere's law, and magnetic dipole approximations. Use when computing B-fields from arbitrary current geometries, exploiting symmetry with Ampere's law, analyzing superposition of multiple sources, or characterizing…

pjt222/agent-almanac · 79 tokens

analyze-magnetic-levitation

Analyze magnetic levitation systems by applying Earnshaw's theorem to determine whether passive static levitation is possible, then identifying the appropriate circumvention mechanism (diamagnetic, superconducting, active feedback, or spin-stabilized). Use when evaluating maglev transport, magnetic bearings…

pjt222/agent-almanac · 105 tokens

build-sequential-circuit

Build sequential (stateful) logic circuits including latches, flip-flops, registers, counters, and finite state machines. Covers SR latch, D and JK flip-flops, binary/BCD/ring counters, and Mealy/Moore FSM design with clock signal and timing analysis. Use when a circuit must remember past inputs, count events, or…

pjt222/agent-almanac · 84 tokens