Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/dliedke/claudecodeextension/claude-mdgit clone --depth 1 https://github.com/dliedke/ClaudeCodeExtensionWhat 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 | $0.04802 | $0.04802 |
| Opus 5 | $0.02401 | $0.02401 |
| Sonnet 5 | $0.00960 | $0.00960 |
| Haiku 4.5 | $0.00480 | $0.00480 |
Grade A, and why
ClaudeCodeExtension 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 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.
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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md - Claude Code Extension for Visual Studio
Project Overview
Visual Studio Extension (VSIX) for VS 2022/2026 — integrates AI code assistants (Claude Code, OpenAI Codex, Cursor Agent, Open Code, Devin, PI, Google Antigravity, and Reasonix) via embedded terminal (Win32 SetParent interop).
- Author: Daniel Carvalho Liedke ([email protected]) | License: MIT
- Repository: https://github.com/dliedke/ClaudeCodeExtension
- Current Version: 160.0 | Target Framework: .NET Framework 4.7.2
MANDATORY: Version & Documentation Updates
Every development session that modifies code MUST update before finishing:
Versioning scheme (since 11.0): each release bumps the MAJOR version by one — 22.0 → 23.0 → 24.0 and so on. Always use .0 as the minor (AssemblyVersion 24.0.0.0, manifest 24.0, README ### Version 24.0). Do not resume 10.x-style minor bumps.
Properties/AssemblyInfo.cs: BumpAssemblyVersionandAssemblyFileVersionsource.extension.vsixmanifest: BumpVersionin<Identity>tagREADME.md: Add### Version X.Yentry at top of## Version History- Style: Short, business-focused. One sentence per bullet (two max). Describe the user-visible feature or fix, not the implementation.
- Avoid: code/file/class/method names, internal selectors, file paths, constants, line numbers, JS snippets, framework jargon (
CoreWebView2,INPUT_RECORD,NavigationCompleted, etc.), step-by-step "how it works" explanations, and PR-description-style root-cause analysis. - Keep: what the user gets ("auto-confirms proxy block screens"), opt-in/opt-out status, and the menu/setting name they interact with.
- Technical details belong in commit messages and
docs/ARCHITECTURE.md, not in release notes. - Other README sections (Features, System Requirements, Provider Menu, Updating, etc.): Edits MUST be minimal. Update only the exact line/bullet affected by the change. Do not rewrite paragraphs, expand explanations, add subsections, reorder content, or restructure tables. If a new provider/setting needs a row, add one row. If a feature description needs a word change, change the word. README is reference doc — keep it slim to avoid file bloat.
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 · 267 lines · 4,802 tokens per session scan A 8d44c42a8132
ClaudeCodeExtension CLAUDE.md is an instructions file published in the GitHub repository dliedke/ClaudeCodeExtension (67 stars, last pushed 5d ago), licensed MIT. It adds 4,802 tokens to every session, about $0.0240 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
gortex CLAUDE.md
Claude Code instructions for zzet/gortex, covering gortex, build & test, codebase overview, discovery (read once, then keep using) and llm provider (powers ask and searchsymbols assist: modes).
cursor-mcp-bridge CLAUDE.md
Instructions for JaimeJunr/cursor-mcp-bridge, covering claude.md, what this is, commands, architecture and engines & tiers (multi-cli).
codeseeker CLAUDE.md
Claude Code instructions for jghiringhelli/codeseeker: Smart Claude Code CLI — semantic search, graph analysis, token-optimized code intelligence. Read .claude/index.md before any task. Load .claude/core.md always.
agentic-playwright selectors.instructions.md
Instructions for idavidov13/agentic-playwright, covering selector strategy, critical, instructions, phase 1: open and authenticate and phase 2: explore like a user.
awesome-copilot-id AGENTS.md
Instructions for GulajavaMinistudio/awesome-copilot-id, covering communication, explanation and documentation, markdown formatting, user communication style and workflow & methodology.
llm-ide-rules pytest-integration-tests.instructions.md
Instructions for iloveitaly/llm-ide-rules, covering pytest integration tests and example integration test.