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/rizowski/unraid-docker-folders/claude-mdgit clone --depth 1 https://github.com/rizowski/unraid-docker-foldersWrote 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/rizowski/unraid-docker-folders/claude-md)<a href="https://agentmods.dev/instructions/rizowski/unraid-docker-folders/claude-md"><img src="https://agentmods.dev/badge/instructions/rizowski/unraid-docker-folders/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.06618 | $0.06618 |
| Opus 5 | $0.03309 | $0.03309 |
| Sonnet 5 | $0.01324 | $0.01324 |
| Haiku 4.5 | $0.00662 | $0.00662 |
Grade C, and why
unraid-docker-folders CLAUDE.md scanned grade C with 1 finding 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
(`resolveAgainst`), *then* check containment. `../../etc/shadow` has no base to How it starts
The opening of the file, as written. The whole thing — 582 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
Unraid Docker Folders - A modern Unraid plugin to replace the outdated folderview2 plugin with Vue 3 frontend, real-time WebSocket updates, and SQLite persistence. Allows organizing Docker containers into folders with drag-and-drop.
Current Status: Shipping. Stable releases are cut from main, prereleases from dev. Beyond folder organization the plugin covers live resource stats, container logs, image update checking and batch pulls, Docker Compose editing and stack grouping, cron schedules, and configuration backups.
UI work: See DESIGN.md for the design system — theme tokens, button vocabulary, modal chrome, and the Unraid CSS reset gotchas. It is normative; follow it for any frontend change.
Design Guardrails (MANDATORY for any UI change)
Before touching any template, CSS, or .page markup, read DESIGN.md and
comply with it. It is a set of hard constraints, not suggestions.
Non-negotiables (full rules + review checklist in DESIGN.md):
- The plugin must look native to Unraid's webgui: dense, flat, border-separated, themed by the user's Unraid theme variables.
- Theme tokens only (from
main.css@theme) — never Tailwind palette classes (bg-blue-500,text-slate-*, …) or hex values in components. - One accent (Unraid's
--header-background). Status colors mean state, never decoration. - No gradients, glassmorphism, glow shadows, or radii above
rounded(4px) on panels. Shadows only on modals/dropdowns. - Type scale is
text-xs/text-sm; dense spacing (p-2/p-3); no hero sections or airy layouts. - Inline stroke SVG icons only; no emoji in the UI; transitions ≤ 200ms and only for state changes.
- Reuse existing patterns (nav-btn, kebab menu, cards, BaseModal) before inventing new ones. Verify on both dark and light Unraid themes.
If a change genuinely requires breaking a rule, state which rule and why in the commit message.
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 · 582 lines · 6,618 tokens per session scan C f6e709f4da14
unraid-docker-folders CLAUDE.md is an instructions file published in the GitHub repository rizowski/unraid-docker-folders (5 stars, last pushed 13d ago), licensed MIT. It adds 6,618 tokens to every session, about $0.0331 per session on Opus 5. A static security scan graded it C with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
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).
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.
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.
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).