Borrowing it
Nothing to install: this file belongs to TimothyVang/verdict-dfir. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TimothyVang/verdict-dfir/master/CLAUDE.mdgit clone --depth 1 https://github.com/TimothyVang/verdict-dfirWrote 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/timothyvang/verdict-dfir/claude-md)<a href="https://agentmods.dev/instructions/timothyvang/verdict-dfir/claude-md"><img src="https://agentmods.dev/badge/instructions/timothyvang/verdict-dfir/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.1 | $0.05628 | $0.05628 |
| Opus 5 | $0.02814 | $0.02814 |
| Sonnet 5 | $0.01126 | $0.01126 |
| Haiku 4.5 | $0.00563 | $0.00563 |
Grade A, and why
verdict-dfir 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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file is the Claude Code operating contract for VERDICT DFIR. It is public-release guidance for running and maintaining the application, not a private development diary.
What VERDICT Is
VERDICT is a DFIR agent that runs inside Claude Code. Point it at supported evidence and it opens a Case, drives the typed read-only MCP tool surface, verifies every Finding, and writes a signed Verdict plus analyst report.
Canonical one-shot path:
bash scripts/setup
scripts/verdict <path-to-evidence>
Interactive Claude Code path:
claude
# then type one of:
/verdict <path-to-evidence>
investigate <path-to-evidence>
Verdict words are strictly scoped:
SUSPICIOUSmeans VERDICT found reportable evidence.INDETERMINATEmeans leads or limited coverage prevent a scoped clearance.NO_EVILmeans no reportable Finding in the artifacts actually examined. It is never a whole-environment clean bill of health.
VERDICT ecosystem — what is what
VERDICT is a local-first DFIR (digital forensics & incident response) agent platform, split into three repos:
| Repo | Role | It is… |
|---|---|---|
caseforge-core |
Headless controller: privacy routing, model selection, structured findings, custody validation, the caseforge CLI. |
the driver |
verdict-opencode |
The agent runtime — a branded fork of opencode; the verdict binary is built from it. |
the engine |
| verdict-dfir-beta / this repo | The forensic toolkit: findevil-mcp (Rust, 34 read-only tools) + findevil-agent-mcp (Python, 14 custody/crypto tools) + DFIR doctrine (agent-config/) + hash-chained custody. Consumed by caseforge via VERDICT_DFIR_HOME. |
the evidence lab (you are here) |
Runtime flow: caseforge (controls + guards) → verdict binary (runs the agent) → this repo's findevil MCP tools (do the forensics) → hash-chained custody → caseforge verify.
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 · 303 lines · 5,628 tokens per session scan A 17f10689cf1c
verdict-dfir CLAUDE.md is an instructions file published in the GitHub repository TimothyVang/verdict-dfir (12 stars, last pushed 4d ago), licensed Apache-2.0. It adds 5,628 tokens to every session, about $0.0281 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-09-04.
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).
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).
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.