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/dissimilis/dirforge/claude-mdgit clone --depth 1 https://github.com/Dissimilis/DirForgeWhat 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.01225 | $0.01225 |
| Opus 5 | $0.00613 | $0.00613 |
| Sonnet 5 | $0.00245 | $0.00245 |
| Haiku 4.5 | $0.00122 | $0.00122 |
Grade A, and why
DirForge 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 2d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Project
DirForge is a stateless, read-only directory listing web app for homelab/NAS use.
- Stack: ASP.NET Core Razor Pages, .NET 10 (
net10.0) - Data model: no database, no persistent application state
- Dependency model: runtime app uses framework built-ins only
- Mission: safely expose files from a configured root with strong defaults
Philosophy
DirForge is intentionally small and opinionated. It is not trying to be a full file platform.
1) Security Before Features
Path traversal prevention, root-constrained resolution, symlink containment, and strict auth handling are mandatory. A feature that weakens these boundaries is not acceptable.
2) Read-Only Means Read-Only
DirForge is a file access and distribution surface, not a file mutation surface. Public endpoints should not write, rename, move, or delete user files.
3) Stateless and Disposable Runtime
In-memory metrics, logs, and one-time-share session state are intentional. Restarting the process should be safe and expected operational behavior.
4) Simplicity Over Cleverness
Prefer direct, readable code over abstractions and micro-optimizations unless there is a measured production problem.
5) Observability Is Product Behavior
Operational endpoints, dashboard, and /metrics are part of the contract. User-visible behavior changes should be reflected in telemetry in the same change.
Non-Negotiable Invariants
- All request paths must remain constrained to
RootPath. - Symlink traversal cannot escape root scope.
- Hide/deny policy must stay consistent across UI, API, WebDAV, S3, and MCP where relevant.
- Auth checks must remain strict and timing-safe where applicable.
- Endpoint surfaces remain read-only unless the project direction explicitly changes.
Architecture Map
Startup and Composition
-
src/DirForge/Program.cs- Configuration load/normalization/validation
- Service graph, middleware order, endpoint mapping
-
src/DirForge/Models/DirForgeOptions.cs -
src/DirForge/Services/DirForgeOptionsResolver.cs -
src/DirForge/Services/DirForgeOptionsValidator.cs
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.
- 2d ago First seen · 161 lines · 1,225 tokens per session scan A 66a474f74fc6
DirForge CLAUDE.md is an instructions file published in the GitHub repository Dissimilis/DirForge (4 stars, last pushed 2mo ago), licensed MIT. It adds 1,225 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
homelab-mcp CLAUDE.md
Instructions for bjeans/homelab-mcp, covering claude development guide for homelab mcp, project overview, core philosophy, project structure and architecture patterns.
mealforge AGENTS.md
AGENTS.md instructions for LooseWireDev/mealforge, covering agent workflow & project conventions, per-app context, spec-driven development, feature development and task execution.
mealforge CLAUDE.md
Claude Code instructions for LooseWireDev/mealforge, covering general guidelines for working with nx, scaffolding & generators and when to use nxdocs.
selfhost-ai CLAUDE.md
Instructions for kossakovsky/selfhost-ai, covering claude.md, project overview, core architecture, key files and installation flow.
homelab-monitor CLAUDE.md
Instructions for SikamikanikoBG/homelab-monitor, covering claude.md and conventions.
better-notion-mcp CLAUDE.md
Instructions for n24q02m/better-notion-mcp, covering better-notion-mcp, cau truc, lenh thuong dung, test don le and mise shortcuts.