Borrowing it
Nothing to install: this file belongs to viknesh20-20/claude-code-tool-kit. 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/viknesh20-20/claude-code-tool-kit/master/CLAUDE.mdgit clone --depth 1 https://github.com/viknesh20-20/claude-code-tool-kitWrote 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/viknesh20-20/claude-code-tool-kit/claude-md)<a href="https://agentmods.dev/instructions/viknesh20-20/claude-code-tool-kit/claude-md"><img src="https://agentmods.dev/badge/instructions/viknesh20-20/claude-code-tool-kit/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/viknesh20-20/claude-code-tool-kit/claude-md"><img src="https://agentmods.dev/badge/instructions/viknesh20-20/claude-code-tool-kit/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.00686 | $0.00686 |
| Opus 5 | $0.00343 | $0.00343 |
| Sonnet 5 | $0.00137 | $0.00137 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
claude-code-tool-kit 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 5d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Instructions
Universal Claude Code configuration — stack-agnostic, upgradable, shared across all projects. Detailed rules are in
.claude/rules/and auto-load into context.
Environment Detection
Current directory: !pwd
Project files: !ls -1 2>/dev/null | head -20
Git branch: !git branch --show-current 2>/dev/null || echo "not a git repo"
Language hints: !ls package.json requirements.txt Pipfile pyproject.toml go.mod Cargo.toml *.csproj *.sln Gemfile build.gradle pom.xml composer.json mix.exs deno.json 2>/dev/null
Core Principles
- Follow the existing patterns and conventions already present in THIS project
- Detailed standards are in
.claude/rules/— they auto-load per session - When rules conflict with project conventions, project conventions win
File Operations
- Verify directories exist before creating files
- Prefer editing specific sections over rewriting entire files
- Respect .gitignore — never modify ignored file categories
- Follow existing naming conventions in the project
Communication
- Be concise but thorough — explain "why" not just "what"
- Flag potential issues and trade-offs proactively
- Ask clarifying questions rather than assuming
Boundaries
- Do not refactor files outside the current task scope
- Do not install new packages without confirming with the user
- Do not modify lock files manually
- Do not overwrite .env files or secrets
- Do not make architectural changes without discussion
- Do not delete tests, even if currently failing
gstack
The gstack skills are vendored under .claude/skills/gstack/. Use the /browse skill from gstack for all web browsing — never use mcp__claude-in-chrome__* tools.
Available gstack slash commands:
/office-hours, /plan-ceo-review, /plan-eng-review, /plan-design-review, /plan-devex-review, /design-consultation, /design-shotgun, /design-html, /design-review, /devex-review, /review, /ship, /land-and-deploy, /canary, /benchmark, /browse, /connect-chrome, /qa, /qa-only, /setup-browser-cookies, /setup-deploy, /setup-gbrain, /retro, /investigate, /document-release, /codex, /cso, /autoplan, /careful, /freeze, /guard, /unfreeze, /gstack-upgrade, /learn
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.
- 5d ago First seen · 69 lines · 686 tokens per session scan A d35fb3f5055d
claude-code-tool-kit CLAUDE.md is an instructions file published in the GitHub repository viknesh20-20/claude-code-tool-kit (7 stars, last pushed 4mo ago), licensed MIT. It adds 686 tokens to every session, about $0.0034 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-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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.