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.
npx agentmods add skills/daffy0208/ai-dev-standards/iot-developernpx skills add daffy0208/ai-dev-standards --skill iot-developergit clone --depth 1 https://github.com/daffy0208/ai-dev-standardsWhat 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 | $0.00018 | $0.02221 |
| Opus 5 | $0.00009 | $0.01111 |
| Sonnet 5 | $0.00004 | $0.00444 |
| Haiku 4.5 | $0.00002 | $0.00222 |
Grade A, and why
iot-developer 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 yesterday.
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 — 377 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IoT Developer Skill
I help you build IoT applications, connect sensors and devices, and create smart home/industrial IoT solutions.
What I Do
Device Integration:
- Microcontroller programming (Arduino, ESP32)
- Sensor reading and data collection
- Actuator control (motors, LEDs, relays)
- Hardware interfacing
Communication:
- MQTT messaging
- WebSocket connections
- REST API integration
- Bluetooth/WiFi connectivity
IoT Platforms:
- Real-time dashboards
- Device management
- Data logging
- Alerts and automation
MQTT Basics (Web Client)
npm install mqtt
// lib/mqtt-client.ts
import mqtt from 'mqtt'
export class MQTTClient {
private client: mqtt.MqttClient
constructor(brokerUrl: string) {
this.client = mqtt.connect(brokerUrl, {
clientId: `web_${Math.random().toString(16).slice(3)}`,
clean: true,
connectTimeout: 4000
})
this.client.on('connect', () => {
console.log('MQTT connected')
})
this.client.on('error', error => {
console.error('MQTT error:', error)
})
}
subscribe(topic: string, callback: (message: string) => void) {
this.client.subscribe(topic, err => {
if (err) console.error('Subscribe error:', err)
})
this.client.on('message', (receivedTopic, message) => {
if (receivedTopic === topic) {
callback(message.toString())
}
})
}
publish(topic: string, message: string) {
this.client.publish(topic, message)
}
disconnect() {
this.client.end()
}
}
Usage:
'use client'
import { useEffect, useState } from 'react'
import { MQTTClient } from '@/lib/mqtt-client'
export function TemperatureDashboard() {
const [temperature, setTemperature] = useState(0)
const [humidity, setHumidity] = useState(0)
useEffect(() => {
const mqtt = new MQTTClient('ws://broker.hivemq.com:8000/mqtt')
mqtt.subscribe('home/temperature', (msg) => {
setTemperature(parseFloat(msg))
})
mqtt.subscribe('home/humidity', (msg) => {
setHumidity(parseFloat(msg))
})
return () => mqtt.disconnect()
}, [])
return (
<div className="grid grid-cols-2 gap-4">
<div className="p-6 bg-white rounded-lg shadow">
<h3 className="text-gray-600">Temperature</h3>
<p className="text-4xl font-bold">{temperature}°C</p>
</div>
<div className="p-6 bg-white rounded-lg shadow">
<h3 className="text-gray-600">Humidity</h3>
<p className="text-4xl font-bold">{humidity}%</p>
</div>
</div>
)
}
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 377 lines · 18 tokens per session scan A 2ca278178f01
iot-developer is a skill published in the GitHub repository daffy0208/ai-dev-standards (36 stars, last pushed 8mo ago), licensed MIT. It adds 18 tokens to every session and 2,221 once invoked, about $0.0001 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-30.
Other skills, from other repositories
edge-iot
Edge computing, IoT protocols, and embedded systems integration.
ha-merge-queue
Finds open Home Assistant pull requests that are genuinely ready to merge, checking CI, the merge-gate statuses, code-owner approval, merge conflicts, requested changes and unresolved review threads. Use when looking for PRs to merge, doing merge-queue triage, or asking for "quick wins" from the open PR backlog.
bump-dependency
Bumps a Python package dependency across Home Assistant Core integrations, regenerates core requirement files, runs verification tests and prek lint, and prepares a pull request with proper release/compare links.
ha-review
Reviews Home Assistant code changes and provides constructive feedback. Should be used when a review is requested to provide a consistent review behavior and output format. This skill can be used for code reviews in general, not just for GitHub pull requests.
ha-integration-knowledge
Everything you need to know to build, test and review Home Assistant Integrations. If you're looking at an integration, you must use this as your primary reference.
ha-quality-scale-verify
Verifies that a Home Assistant integration follows a specific quality scale rule, checking whether it implements the required patterns, configurations, or code structures defined by the quality scale system. Use when asked to check a rule (e.g. "check if the peblar integration follows the config-flow rule") or to…