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/jantman/docker-zoneminder/claude-mdgit clone --depth 1 https://github.com/jantman/docker-zoneminderWrote 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/jantman/docker-zoneminder/claude-md)<a href="https://agentmods.dev/instructions/jantman/docker-zoneminder/claude-md"><img src="https://agentmods.dev/badge/instructions/jantman/docker-zoneminder/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 | $0.01931 | $0.01931 |
| Opus 5 | $0.00966 | $0.00966 |
| Sonnet 5 | $0.00386 | $0.00386 |
| Haiku 4.5 | $0.00193 | $0.00193 |
Grade A, and why
docker-zoneminder 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 5d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
Docker image for ZoneMinder 1.38.4 (video surveillance) on Debian 13 (Trixie), using Apache + PHP 8.4. ZoneMinder is compiled from source in a multi-stage Docker build. Requires an external MySQL/MariaDB database (not bundled). Includes the ZM Event Notification Server (ZMES) — zmeventnotificationNg 7.0.29 with pyzmNg 2.5.1 — for event-driven object detection via WebSocket on port 9000, and go2rtc for WebRTC/MSE/HLS live streaming. This is a personal WIP project (MIT license).
This image ships forks, not upstream releases, and is released that way on purpose —
waiting on upstream would have blocked a release of work already soaked on live traffic.
Releases built this way carry a -fork version suffix. Both pins are by SHA:
| Component | Pinned to | PR |
|---|---|---|
| zmeventnotificationNg | jantman/zmeventnotificationNg @ issues/48 |
ZoneMinder/zmeventnotificationNg#49 — joins config zone patterns onto ZM zone geometry by name |
| pyzmNg | jantman/pyzmNg @ integration/66-68 |
#69 zone_match_strategy (used here) + #67 GPU fallback (gateway-side, carried for parity) |
Neither fork bumps a version string, so the build asserts a marker symbol from each
(normalize_zone_name, ZoneMatchStrategy) rather than trusting the pin. Keep those
assertions for as long as the pins are forks — they are the only thing that would catch a
silently wrong ref, whose sole symptom is zone patterns quietly not applying.
Both forks carry an annotated tag on the pinned commit — image-pin-pr49 and
image-pin-pr67-pr69 — because the PR branches will be deleted once the PRs merge, and an
unreachable commit means this image can no longer be rebuilt. Do not delete those tags
while a released image pins them. Restore the upstream tag / PyPI pin and drop the -fork
suffix once the PRs are released.
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.
- 5d ago First seen · 127 lines · 1,931 tokens per session scan A d2ea487067a4
docker-zoneminder CLAUDE.md is an instructions file published in the GitHub repository jantman/docker-zoneminder (24 stars, last pushed 7d ago), licensed MIT. It adds 1,931 tokens to every session, about $0.0097 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
CopilotTraining infrastructure.instructions.md
Infrastructure and DevOps standards for Docker, Kubernetes, Terraform, and CI/CD workflows.
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.
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.