Borrowing it
Nothing to install: this file belongs to liortesta/ClawdAgent. 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/liortesta/ClawdAgent/main/CLAUDE.mdgit clone --depth 1 https://github.com/liortesta/ClawdAgentWrote 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/liortesta/clawdagent/claude-md)<a href="https://agentmods.dev/instructions/liortesta/clawdagent/claude-md"><img src="https://agentmods.dev/badge/instructions/liortesta/clawdagent/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.03271 | $0.03271 |
| Opus 5 | $0.01636 | $0.01636 |
| Sonnet 5 | $0.00654 | $0.00654 |
| Haiku 4.5 | $0.00327 | $0.00327 |
Grade C, and why
ClawdAgent CLAUDE.md scanned grade C with 1 finding 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 3d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
| PreToolUse → Bash | Before shell command | Blocks dangerous commands (rm -rf, DROP, etc.) | How it starts
The opening of the file, as written. The whole thing — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Configuration — Claude Code MEGA Setup
This file is loaded automatically at the start of every Claude Code session. It serves as the "constitution" — all agents and commands follow these rules.
Architecture
- Language: [DETECT_ON_SETUP]
- Framework: [DETECT_ON_SETUP]
- Package Manager: [DETECT_ON_SETUP]
- Test Framework: [DETECT_ON_SETUP]
- Database: [DETECT_ON_SETUP]
- Deployment: [DETECT_ON_SETUP]
Key Commands
[pkg] run dev— Start dev server[pkg] run build— Production build[pkg] run test— Run tests[pkg] run lint— Lint check[pkg] run type-check— Type checking
Code Standards
- TypeScript strict mode when applicable
- No
anytypes — useunknownor proper typing - All exports must have JSDoc/docstrings
- Max file length: 300 lines — split if larger
- Prefer composition over inheritance
- Error handling: never swallow errors silently
- All API endpoints must have input validation
- Environment variables: never hardcode secrets
- Use meaningful variable names — no single-letter vars except loop counters
Workflow Rules
- For ANY task >50 lines of code: Enter Plan Mode FIRST (Shift+Tab)
- For ANY commit: All tests must pass (enforced by Stop hook)
- For ANY architecture decision: Use the CTO agent for evaluation
- For ANY security-related code: Mandatory security-auditor agent review
- After ANY correction from user: Update this file under "Self-Correction Rules"
- Use subagents for parallel work when tasks are independent
- Use background tasks (Ctrl+B) for long-running processes
- Use Playwright MCP for visual/UI verification when available
- ALWAYS "prove it works" before marking any task done
Background Task Rules
- ALWAYS run dev servers in background
- ALWAYS run watch processes in background
- Run security scans in background while developing
- Use /tasks to monitor running background agents
Memory Management
- After each session, run /wrap-up to consolidate learnings
- Update this file with key architectural decisions
- Memory priority: Security rules > Architecture > Code style > Preferences
- When Claude makes a mistake and is corrected, add rule to Self-Correction section
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.
- 3d ago First seen · 288 lines · 3,271 tokens per session scan C e12e1389fb1f
ClawdAgent CLAUDE.md is an instructions file published in the GitHub repository liortesta/ClawdAgent (11 stars, last pushed 10d ago), licensed Apache-2.0. It adds 3,271 tokens to every session, about $0.0164 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
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.