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 instructions/openipc/firmware/claude-mdgit clone --depth 1 https://github.com/OpenIPC/firmwareWhat 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.04039 | $0.04039 |
| Opus 5 | $0.02020 | $0.02020 |
| Sonnet 5 | $0.00808 | $0.00808 |
| Haiku 4.5 | $0.00404 | $0.00404 |
Grade A, and why
firmware 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 3d 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 — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Orientation for anyone — human or AI coding assistant — about to change this repository.
AGENTS.md is a symlink to this file, so Claude Code, Codex, Cursor, Copilot and the rest read
the same text.
This file tells you where things are and what will get a pull request closed. It does not replace
the review contract: best_practices.md holds the judgement calls, each one traced to a pull
request that was actually closed, and pr_compliance_checklist.yaml holds the binary gates. Read
best_practices.md before changing anything under general/.
What this is
OpenIPC firmware is a Buildroot external tree that builds images for IP cameras across 13
SoC-vendor trees. Buildroot itself is not vendored — make downloads the version pinned in
BR_VER at the top of the Makefile into $(TARGET)/buildroot-$(BR_VER)/. When you need
Buildroot's own package/, linux/ or toolchain/ logic, read it there; it is not in this repo.
make list prints every board configuration. Do not trust a board count written down anywhere,
including here — the list moves.
One consequence drives every rule below. general/overlay/ and general/package/ are shared, so
a single file there reaches every camera of a family. Those cameras sit in places nobody can
physically reach, there is no staged rollout, and a bad change is discovered only after
sysupgrade has already written it to flash. Weight a change by how many cameras the file you
touched reaches, not by how many lines you changed.
Before you start: is this the right repository?
The most common reason a well-made pull request gets closed here is that it belongs somewhere else. Check this first — it costs a minute and can save an evening.
| What you are changing | Where it goes |
|---|---|
| Kernel source and kernel patches | [OpenIPC/linux][linux] |
| Support for one specific retail camera model | [OpenIPC/builder][builder] |
| Probing, identification, bring-up tooling | [OpenIPC/ipctool][ipctool] |
| A bug in the video stream itself | majestic's maintainers, not a shim here |
| Documentation, device notes, how-tos | [OpenIPC/wiki][wiki], [docs][docs] |
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.
- 3d ago First seen · 292 lines · 4,039 tokens per session scan A 67c17fa41cec
firmware CLAUDE.md is an instructions file published in the GitHub repository OpenIPC/firmware (2,172 stars, last pushed 3d ago), licensed MIT. It adds 4,039 tokens to every session, about $0.0202 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 instructions, from other repositories
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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.