Borrowing it
Nothing to install: this file belongs to R00T-Kim/SCOUT. 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/R00T-Kim/SCOUT/main/CLAUDE.mdgit clone --depth 1 https://github.com/R00T-Kim/SCOUTWrote 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/r00t-kim/scout/claude-md)<a href="https://agentmods.dev/instructions/r00t-kim/scout/claude-md"><img src="https://agentmods.dev/badge/instructions/r00t-kim/scout/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.01596 | $0.01596 |
| Opus 5 | $0.00798 | $0.00798 |
| Sonnet 5 | $0.00319 | $0.00319 |
| Haiku 4.5 | $0.00160 | $0.00160 |
Grade A, and why
SCOUT 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 8d 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 — 130 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
SCOUT (AIEdge) is a deterministic firmware-to-exploit evidence engine. It takes firmware blobs as input and produces hash-anchored evidence artifacts through a 42-stage sequential pipeline — from unpacking through vulnerability discovery to exploit chain verification. SCOUT is the evidence-production layer; a separate orchestrator (Terminator) applies LLM judgment and dynamic validation on top via firmware_handoff.json.
Key constraints: Pure Python 3.10+ with zero pip dependencies (stdlib only). External tools (binwalk, QEMU, FirmAE, docker) are runtime-optional.
Build, Test, and Run Commands
# CLI help
./scout --help
# Full analysis (all features enabled by default)
./scout analyze firmware.bin
# Suppress real-time progress output (CI/scripted use)
./scout analyze firmware.bin --quiet
# Deterministic analysis (no LLM)
./scout analyze firmware.bin --no-llm
# With specific stages
./scout analyze firmware.bin --no-llm \
--stages tooling,extraction,structure,carving,firmware_profile,inventory
# Pre-extracted rootfs bypass (when extraction is weak)
./scout analyze firmware.img --no-llm --rootfs /path/to/extracted/rootfs
# 8MB canonical track (truncated input for quick profiling)
./scout analyze-8mb firmware.bin --no-llm
# Rerun specific stages on existing run
./scout stages aiedge-runs/<run_id> --no-llm --stages inventory
# Run tests
pytest -q # full suite
pytest -q tests/test_inventory.py # single module
pytest -q tests/test_inventory.py::test_func # single test
# Linting (ruff configured via pyproject.toml)
ruff check src/
# Type checking (pyright configured via pyrightconfig.json)
pyright src/
# Quality and verification
./scout corpus-validate aiedge-runs/<run_id>
./scout quality-metrics aiedge-runs/<run_id>
./scout quality-gate aiedge-runs/<run_id>
./scout release-quality-gate aiedge-runs/<run_id>
scripts/release_gate.sh --run-dir aiedge-runs/<run_id>
python3 scripts/verify_analyst_digest.py --run-dir aiedge-runs/<run_id>
python3 scripts/verify_verified_chain.py --run-dir aiedge-runs/<run_id>
# TUI dashboard
./scout tui aiedge-runs/<run_id> --interactive # interactive mode
./scout tw aiedge-runs/<run_id> -t 2 # live-refresh (watch)
./scout ti # interactive, latest run
./scout to # once mode
./scout t # latest run
# Serve report viewer
./scout serve aiedge-runs/<run_id>
# MCP server for AI agent integration
./scout mcp [--project-id <run_id>]
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.
- 8d ago First seen · 130 lines · 1,596 tokens per session scan A d8ef6449864d
SCOUT CLAUDE.md is an instructions file published in the GitHub repository R00T-Kim/SCOUT (11 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 1,596 tokens to every session, about $0.0080 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
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.
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).
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).
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.
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.