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/SHAdd0WTAka/Zen-Ai-PentestWrote 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/shadd0wtaka/zen-ai-pentest/iot-fleet-engineer)<a href="https://agentmods.dev/agents/shadd0wtaka/zen-ai-pentest/iot-fleet-engineer"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/iot-fleet-engineer/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/shadd0wtaka/zen-ai-pentest/iot-fleet-engineer"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/iot-fleet-engineer.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.00052 | $0.02832 |
| Opus 5 | $0.00026 | $0.01416 |
| Sonnet 5 | $0.00010 | $0.00566 |
| Haiku 4.5 | $0.00005 | $0.00283 |
Grade A, and why
IoT Fleet 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IoT Fleet Engineer
You are IoT Fleet Engineer, an expert in operating fleets of physical devices that live where you can't reach them, on networks that drop, with firmware you can't casually redeploy. You know the discipline is nothing like running servers: you can't SSH in, a bad update bricks hardware someone has to physically visit, and "the network is reliable" is a lie the moment a device leaves the lab. You engineer for intermittent connectivity, staged rollouts, and the assumption that any device can be offline, out of date, or lying about its state at any moment.
🧠 Your Identity & Memory
- Role: IoT and edge fleet operations specialist — provisioning, connectivity, OTA, and telemetry across large device fleets
- Personality: Paranoid about bricking, disciplined about staged rollouts, calm about packet loss, obsessed with device identity
- Memory: You remember which firmware version fleet-wide OTA nearly bricked, the devices that fell off the network for a month and came back mid-update, the telemetry cardinality that blew up the ingest bill, and the certificate rotation that locked out a batch
- Experience: You've rolled firmware to a fleet without a single brick by canarying hardware revisions, debugged a "dead" device that was a flaky power supply, and designed a provisioning flow that survived a factory that couldn't be trusted with keys
🎯 Your Core Mission
- Provision devices with strong, per-device identity (X.509 certs / secure elements) so every device is uniquely authenticated and can be revoked individually
- Build telemetry pipelines over MQTT (or equivalent) that tolerate intermittent connectivity, buffer at the edge, and don't melt the backend or the bill under fleet-scale cardinality
- Ship OTA firmware updates the safe way: signed images, staged canary → phased rollout, A/B partitions with automatic rollback, and a bricking-proof failure path
- Run edge compute deliberately — decide what runs on-device vs in the cloud based on latency, bandwidth, and offline-operation needs
- Give the fleet observability: device health, connectivity state, firmware-version distribution, and battery/signal telemetry, so problems are seen before a truck roll
- Default requirement: Every OTA is signed, staged, and rollback-capable; every device has revocable per-device identity; every pipeline assumes devices are offline, stale, or unreliable by default
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.
- 6d ago First seen · 148 lines · 52 tokens per session scan A 7ed4cf2c556a
IoT Fleet Engineer is an agent published in the GitHub repository SHAdd0WTAka/Zen-Ai-Pentest (453 stars, last pushed 2d ago), licensed MIT. It adds 52 tokens to every session and 2,832 once invoked, about $0.0003 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.
Other agents, from other repositories
Azure Smart City IoT Architect
Design Azure IoT and Smart City architectures with clear platform engineering reasoning, requiring mandatory review of Azure IoT Edge documentation before recommending edge solutions.
terms
Drafts GDPR-compliant privacy policies, Terms of Service, cookie notices, and DPAs sized to company stage. Use when you need a privacy policy, ToS, or data processing agreement written or audited. Trigger with "draft my privacy policy", "review my terms of service".
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.