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/lidless-labs/immichctrl/claude-mdgit clone --depth 1 https://github.com/lidless-labs/immichctrlWrote 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/lidless-labs/immichctrl/claude-md)<a href="https://agentmods.dev/instructions/lidless-labs/immichctrl/claude-md"><img src="https://agentmods.dev/badge/instructions/lidless-labs/immichctrl/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.00514 | $0.00514 |
| Opus 5 | $0.00257 | $0.00257 |
| Sonnet 5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
immichctrl 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- adguardctrl CLAUDE.md — 100% identical, 0 lines differ
- n8nctrl CLAUDE.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md - Claude Code Rules
Project rules
- Follow
AGENTS.mdin this repo. This file is the Claude Code-specific bridge; cross-harness behavior lives inAGENTS.md.
Memory handoff
The canonical memory owner on this repo is claude. Claude Code may keep local session context, but durable knowledge must be written as a Memory Handoff in .claude/memory-handoffs/. Full contract in AGENTS.md.
At the end of any substantial task, check whether the session produced durable knowledge. If yes, write a handoff using .claude/memory-handoffs/TEMPLATE.md. Do not wait to be reminded.
Brigade work loop (Mandatory)
This repo is Brigade-wired. Route real work through Brigade so its outcome ledger fills. Invoke the brigade-work skill: brigade work brief at the start; run verifications via brigade work verify run --target . --command "<test>" (not raw) when the result should count; then brigade outcome capture <skill-or-card-id> --run-id latest; handoff at the end. If brigade outcome rank says "ranking: none", work is not flowing through Brigade. Full contract in AGENTS.md.
For large scoping work, invoke ultra-work-scout first. It is installed with the built-in Brigade skills and keeps Scout delegation tied to verified Brigade work.
Closeout
- Report the exact verification command you ran.
- If verification could not run, state the blocker.
- If a Memory Handoff was warranted, confirm where it landed.
Tool use
- Say it = call it. If you say you will do something that requires a tool, call the tool in the same turn. Silent intent is a lie.
- After a tool failure, emit a one-line status or call a different tool within 30 seconds. Do not silently reason for minutes.
Git
- Do not add
Co-Authored-Byor AI-attribution trailers to commits, PR bodies, or public docs. - Use conventional commits.
- Never bypass pre-push hooks (
--no-verify) unless the user has explicitly accepted the risk. - Never push to
maindirectly on shared repos. Feature branch + PR.
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 · 42 lines · 514 tokens per session scan A 287a5d6ba58f
immichctrl CLAUDE.md is an instructions file published in the GitHub repository lidless-labs/immichctrl (5 stars, last pushed 1mo ago), licensed MIT. It adds 514 tokens to every session, about $0.0026 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
artel CLAUDE.md
Instructions for NicolasPrimeau/artel, covering artel, what it is, stack, layout and core primitives.
state-memory-mcp copilot-instructions.md
Instructions for putervision/state-memory-mcp, covering state memory (state-memory-mcp), 1. priority order, 2. when to write to the graph, 3. workflow pattern and 4. codebase seeding on initialization.
toon-memory AGENTS.md
Instructions for LuiggiVal08/toon-memory, covering agents.md, build & verify, architecture, smarter memory pattern and visual memory pattern.
mnemo-mcp AGENTS.md
Instructions for n24q02m/mnemo-mcp, covering agents.md - mnemo-mcp, commands, setup, lint & type check and fix.
petromcp CLAUDE.md
Instructions for ameyxd/petromcp, covering petromcp — project memory, what this is, where we are, conventions and decisions and why.
munin-memory CLAUDE.md
Claude Code instructions for Magnus-Gille/munin-memory, a project described as: Persistent memory for AI assistants, self-hosted and provider-portable. MCP server with SQLite + FTS5 + sqlite-vec.