Borrowing it
Nothing to install: this file belongs to mitra42/frugal-iot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mitra42/frugal-iot/main/CLAUDE.mdgit clone --depth 1 https://github.com/mitra42/frugal-iotWrote 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/instructions/mitra42/frugal-iot/claude-md)<a href="https://agentmods.dev/instructions/mitra42/frugal-iot/claude-md"><img src="https://agentmods.dev/badge/instructions/mitra42/frugal-iot/claude-md.svg" alt="Measured on agentmods" 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.16662 | $0.16662 |
| Opus 5 | $0.08331 | $0.08331 |
| Sonnet 5 | $0.03332 | $0.03332 |
| Haiku 4.5 | $0.01666 | $0.01666 |
Grade A, and why
frugal-iot CLAUDE.md 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 8d 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 — 1,107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frugal-IoT Library
A platform for affordable, easily built sensor networks running on ESP32/ESP8266 microcontrollers. Library version: 0.1.6. MIT licence. Author: Mitra Ardron.
Wiki: https://github.com/mitra42/frugal-iot/wiki Repo: https://github.com/mitra42/frugal-iot
Compatibility
Every example .ino file must work in both:
- Arduino IDE — open the
.inodirectly; dependencies installed via Library Manager - PlatformIO — referenced via
lib_deps = Frugal-IoT@^0.1.6inplatformio.ini
Each example directory contains a platform.h file alongside the .ino. This file is
auto-generated from the example's platformio.ini by running scripts/prerelease.bash
(which calls scripts/generate_platform_h.py). It converts -D FLAG=value build flags into
#define statements and wraps board-specific defines in #ifdef ARDUINO_BOARD_NAME guards.
- PlatformIO reads flags directly from
platformio.ini;platform.his not used. - Arduino IDE picks
platform.hup because_settings.hincludes it whenPLATFORMIOis undefined — the.inodoes not need to (and on ESP8266 could not; see below).
Do not hand-edit platform.h — regenerate it by re-running scripts/prerelease.bash after
changing platformio.ini.
Test-compiling an example for Arduino
scripts/arduino_compile.bash <example> <env> compiles an example exactly as the Arduino IDE
would, from the command line via arduino-cli (same cores, libraries and sketchbook as the IDE —
nothing needs opening). Run it from the scripts directory:
cd lib/Frugal-IoT/scripts
./arduino_compile.bash commonroom nodemcu_tambak
./arduino_compile.bash --list # every example and its environments
./arduino_compile.bash --install-deps # core + library.properties deps (ESP32 core is >1GB)
It passes --library .. so the working tree is compiled, not whatever stale copy sits in
~/Documents/Arduino/libraries. It regenerates platform.h first, and checks two things a bare
"exit 0" would hide:
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.
- 8d ago First seen · 1,107 lines · 16,662 tokens per session scan A 8361aeec27c9
frugal-iot CLAUDE.md is an instructions file published in the GitHub repository mitra42/frugal-iot (10 stars, last pushed 7d ago), licensed MIT. It adds 16,662 tokens to every session, about $0.0833 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.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.