Borrowing it
Nothing to install: this file belongs to YuriNachos/claude-scope. 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/YuriNachos/claude-scope/main/CLAUDE.mdgit clone --depth 1 https://github.com/YuriNachos/claude-scopeWrote 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/yurinachos/claude-scope/claude-md)<a href="https://agentmods.dev/instructions/yurinachos/claude-scope/claude-md"><img src="https://agentmods.dev/badge/instructions/yurinachos/claude-scope/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.00845 | $0.00845 |
| Opus 5 | $0.00423 | $0.00423 |
| Sonnet 5 | $0.00169 | $0.00169 |
| Haiku 4.5 | $0.00085 | $0.00085 |
Grade A, and why
claude-scope 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 7d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Claude Code CLI tool that displays status information in the terminal.
Version: v0.8.44
Quick Commands
npm run build # Build the project
npm test # Run all tests
npx @biomejs/biome check --write ./src # Format & lint
npm version patch # Bump version (patch/minor/major)
Installation & Default Config
On first run, claude-scope automatically creates ~/.claude-scope/config.json with default settings:
- Layout:
rich(3 lines) - Display Style:
balanced - Theme:
monokai
Users can customize via:
claude-scope quick-config # Interactive configuration menu
Or manually edit ~/.claude-scope/config.json.
Tech Stack
- Language: TypeScript (Node.js)
- Minimal runtime dependencies - systeminformation for system monitoring
- Formatter: Biome for linting and formatting
- Package manager: npm
Architecture (Overview)
This project uses a widget registry pattern with Dependency Inversion:
IWidgetinterface - all widgets implement thisWidgetRegistry- central widget lifecycle managerWidgetFactory- centralized widget creationRenderer- multi-line rendering with error boundaries
Key files: src/core/types.ts, src/core/widget-registry.ts, src/core/widget-factory.ts
Detailed architecture: See docs/ARCHITECTURE.md
Widget Development
To add a new widget:
- Implement
IWidgetinterface (or extendStdinDataWidget) - Add to
WidgetFactoryinsrc/core/widget-factory.ts - Create styles in
styles.tsusingStyleMappattern - Use
DEFAULT_THEME(Monokai) for colors
Widget documentation: See docs/WIDGETS.md for all widgets, styles, and examples
Code Conventions
- File size: Keep <~500 LOC; split/refactor as needed
- Types: Avoid
any; use proper TypeScript types - Imports: ES modules (
import/export), organized alphabetically - Error handling: Widgets should return
nullon failure - Testing: >80% coverage for core, >60% for widgets
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.
- 7d ago First seen · 120 lines · 845 tokens per session scan A 5cf9da567735
claude-scope CLAUDE.md is an instructions file published in the GitHub repository YuriNachos/claude-scope (8 stars, last pushed 1mo ago), licensed MIT. It adds 845 tokens to every session, about $0.0042 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
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.