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/dylan-isaac/claude-code-unraid/claude-mdgit clone --depth 1 https://github.com/dylan-isaac/claude-code-unraidWrote 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/dylan-isaac/claude-code-unraid/claude-md)<a href="https://agentmods.dev/instructions/dylan-isaac/claude-code-unraid/claude-md"><img src="https://agentmods.dev/badge/instructions/dylan-isaac/claude-code-unraid/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.01227 | $0.01227 |
| Opus 5 | $0.00613 | $0.00613 |
| Sonnet 5 | $0.00245 | $0.00245 |
| Haiku 4.5 | $0.00123 | $0.00123 |
Grade A, and why
claude-code-unraid 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides context for Claude Code when helping maintain, optimize, and troubleshoot an Unraid server environment.
Initial Server Assessment
When first connecting to an Unraid server, Claude should proactively assess:
-
Hardware Configuration
- CPU, RAM, storage devices, network interfaces
- Use commands like
cat /proc/cpuinfo,free -h,lsblk,ip a
-
Unraid Version and Setup
- Current Unraid version and update status
- Array configuration (number of drives, parity, cache)
- Check with
cat /etc/unraid-version,mdcmd status
-
Docker Environment
- Running containers and resource usage
- Docker network configuration
- Use
docker ps,docker stats,docker network ls
-
VM Configuration
- Running VMs and resource allocation
- Use
virsh list --all,virsh dominfo <vm_name>
-
Plugin Inventory
- Installed plugins and their versions
- Look in
/boot/config/plugins/
-
Network Configuration
- Network settings, port forwarding, firewall rules
- Check
/etc/network/, UI settings via API
Common Maintenance Tasks
System Health Monitoring
# Check array status
mdcmd status
# Check SMART status of all drives
for d in $(ls /dev/sd*); do smartctl -a $d | grep -E "Device Model|Serial Number|User Capacity|SMART overall-health|Current Temperature"; done
# Check system temperatures
sensors
# Monitor system resource usage
top -c
htop
Docker Management
# Update all Docker containers
docker container ls -a | grep -v CONTAINER | awk '{print $1}' | xargs -I {} docker update --restart=always {}
# Prune unused Docker resources
docker system prune -a
# View container logs
docker logs <container_name>
Backup Management
# Check backup status
ls -la /mnt/user/backups/
# Run manual backup
rsync -avh --progress /path/to/source /mnt/user/backups/destination
# Verify backup integrity
md5sum /mnt/user/backups/important_file.tar.gz
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 · 175 lines · 1,227 tokens per session scan A 43cb04b5dae5
claude-code-unraid CLAUDE.md is an instructions file published in the GitHub repository dylan-isaac/claude-code-unraid (2 stars, last pushed 1y ago), licensed MIT. It adds 1,227 tokens to every session, about $0.0061 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
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.