Borrowing it
Nothing to install: this file belongs to MinhThang1009/dotclaude. 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/MinhThang1009/dotclaude/main/CLAUDE.mdgit clone --depth 1 https://github.com/MinhThang1009/dotclaudeWrote 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/minhthang1009/dotclaude/claude-md)<a href="https://agentmods.dev/instructions/minhthang1009/dotclaude/claude-md"><img src="https://agentmods.dev/badge/instructions/minhthang1009/dotclaude/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.01212 | $0.01212 |
| Opus 5 | $0.00606 | $0.00606 |
| Sonnet 5 | $0.00242 | $0.00242 |
| Haiku 4.5 | $0.00121 | $0.00121 |
Grade A, and why
dotclaude 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Personal Guidelines (Global)
Loaded into EVERY session. Keep it short — if removing a line still leaves Claude doing the right thing, that line should go.
📝 First-person template convention: This file is user-config that Claude Code loads into EVERY session. The pronoun "I" in the content below = the USER (whoever copies this file into
~/.claude/CLAUDE.md), "you" = Claude. The first-person voice is intentional, following the Claude Code prompt convention — it helps Claude read the instructions as if speaking to itself. When reading the repo for the first time (before copying), substitute "I" = yourself to grasp the intent correctly.
Language
- Default Vietnamese, keep technical terms in English. Details in
communication.md§Vietnamese vs English.
Working Style
- When a plan is needed → the single threshold lives in
plan.md§When to Create a Plan. Plan needed → draft the plan, wait for my approval; each step in the form[Step] → verify: [check]. - Unsure of intent → ASK, don't guess. One question beats 10 minutes of fixing the wrong thing.
- After a change → SELF-CHECK test/lint/typecheck if available. Don't report "done" before verifying.
- I say "ultrathink" → an official keyword; Claude Code adds an in-context instruction requesting deeper reasoning for that turn (the effort level does NOT change). The phrases "think"/"think hard"/"think more" are NOT keywords — treat them as plain text.
- Subagent results, git state, external deps → see details in
verification.md.
Response Style
- Concise. Diff/code FIRST, explanation AFTER. Details in
communication.md.
Code
- Details in
coding-standards.md. Summary: read before writing, follow codebase conventions, YAGNI, surgical changes, don't add a dependency without asking.
Git
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 · 70 lines · 1,212 tokens per session scan A 49acc0c0bfcb
dotclaude CLAUDE.md is an instructions file published in the GitHub repository MinhThang1009/dotclaude (20 stars, last pushed 1mo ago), licensed MIT. It adds 1,212 tokens to every session, about $0.0061 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.