Borrowing it
Nothing to install: this file belongs to dzcorp/FerrisScope. 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/dzcorp/FerrisScope/main/CLAUDE.mdgit clone --depth 1 https://github.com/dzcorp/FerrisScopeWrote 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/dzcorp/ferrisscope/claude-md)<a href="https://agentmods.dev/instructions/dzcorp/ferrisscope/claude-md"><img src="https://agentmods.dev/badge/instructions/dzcorp/ferrisscope/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.08072 | $0.08072 |
| Opus 5 | $0.04036 | $0.04036 |
| Sonnet 5 | $0.01614 | $0.01614 |
| Haiku 4.5 | $0.00807 | $0.00807 |
Grade A, and why
FerrisScope 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 6d 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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Operating notes for Claude Code working in this repo. The user-facing pitch, install, layout, and build instructions live in README.md. This file is the how — rules, conventions, and recipes specific to changing the codebase.
Naming — don't "fix" these
The display name is FerrisScope (mixed case). Everything technical stays lowercase: crates (ferrisscope-core, ferrisscope-kube-ext, ferrisscope-agent, ferrisscope-app), the binary ferrisscope, the Tauri identifier dev.ferrisscope.desktop (Tauri 2 warns against an .app suffix on macOS), disk paths under ~/.config/ferrisscope/, and the SSA field manager constant "ferrisscope" (fetch::FIELD_MANAGER).
The core crate must stay Tauri-free so a future TUI / CLI can reuse the engine. If you're adding tauri to core/Cargo.toml, stop and reconsider.
Hard architectural rules
- One reflector per
(cluster, resource_kind). Never start a second watch for data already cached. - Reflectors are lazy — started on first subscribe, torn down a few seconds after the last unsubscribe.
- Frontend is a mirror, not a source of truth. All canonical state lives in Rust.
- A "cluster" owns a task supervisor. Disconnecting aborts the supervisor — no orphaned tasks, no leaked sockets.
- Frontend business logic budget is near zero. View state in Zustand; everything else over Tauri commands.
Think it through before shipping
When asked to build, fix, or improve something, actively look for ways it can break before reporting done. Don't stop at "the happy path compiles."
- Walk the failure modes. Empty / missing / malformed input. Concurrency and cancellation. Who frees the resource. 403/404/409/410 from the apiserver. Long names, missing namespace, disconnected cluster, stale reflector.
- Fix root causes, not symptoms. For bugs, ask why the bad state became reachable before patching where it surfaced. Add a regression test.
- Finish the loop. Loading, empty, error, and stale states are part of the feature — a button with no disabled state during in-flight work is unfinished.
- Surface what you didn't cover. Wrong assumptions, untested UI paths, related bugs you spotted — name them in the response rather than implying success.
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.
- 6d ago First seen · 278 lines · 8,072 tokens per session scan A 22b916235d3d
FerrisScope CLAUDE.md is an instructions file published in the GitHub repository dzcorp/FerrisScope (11 stars, last pushed 6d ago), licensed Apache-2.0. It adds 8,072 tokens to every session, about $0.0404 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-30.
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.