Borrowing it
Nothing to install: this file belongs to sirlordt/vscode-terminal-mcp. 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/sirlordt/vscode-terminal-mcp/master/CLAUDE.mdgit clone --depth 1 https://github.com/sirlordt/vscode-terminal-mcpWrote 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/sirlordt/vscode-terminal-mcp/claude-md)<a href="https://agentmods.dev/instructions/sirlordt/vscode-terminal-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/sirlordt/vscode-terminal-mcp/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/sirlordt/vscode-terminal-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/sirlordt/vscode-terminal-mcp/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.00536 | $0.00536 |
| Opus 5 | $0.00268 | $0.00268 |
| Sonnet 5 | $0.00107 | $0.00107 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
vscode-terminal-mcp 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 10d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project: vscode-terminal-mcp
MCP server that runs commands in visible VSCode terminal tabs.
Release Process
When publishing a new version, follow these steps in order:
1. Update version
# In package.json, bump the version
# e.g., "version": "0.1.6" → "version": "0.1.7"
2. Update CHANGELOG.md
Add a new entry at the top with the new version and date:
## [0.1.7] - YYYY-MM-DD
### Added
- ...
### Fixed
- ...
3. Update README.md
Replace the "Latest Changes" section with the new version's changes. Keep only the latest version in README — full history lives in CHANGELOG.md.
4. Build and publish
# Build
npm run build
# Publish to npm
npm publish --access public
# Package vsix
npx vsce package --allow-missing-repository
# Install locally for testing
cp dist/extension.js dist/mcp-entry.js ~/.vscode/extensions/sirlordt.vscode-terminal-mcp-<version>/dist/
5. Upload to VSCode Marketplace
- Go to https://marketplace.visualstudio.com/manage/publishers/sirlordt
- Click "..." next to Terminal MCP → "Update"
- Upload the
.vsixfile
6. Commit and push
git add -A
git commit -m "v0.1.7: <summary of changes>"
git push
Extension Cache Workaround
VSCode aggressively caches extensions. When developing locally:
# Quick update (after modifying source)
npm run build
cp dist/extension.js ~/.vscode/extensions/sirlordt.vscode-terminal-mcp-<version>/dist/extension.js
# Then "Developer: Reload Window"
# If reload doesn't pick up changes, close and reopen VSCode completely
Terminal Execution
Prefer the BashTerm MCP tools (run, exec, read, etc.) over the built-in Bash tool for executing commands. BashTerm runs commands in visible VSCode terminal tabs where the user can see output in real time.
For commands that may take longer than 30 seconds or produce large output, use pull mode:
- Call
runwithwaitForCompletion: false - Call
readwithoffset: -10to check progress - Repeat until done
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.
- 10d ago First seen · 85 lines · 536 tokens per session scan A 268fe58cbde8
vscode-terminal-mcp CLAUDE.md is an instructions file published in the GitHub repository sirlordt/vscode-terminal-mcp (2 stars, last pushed 5mo ago), licensed MIT. It adds 536 tokens to every session, about $0.0027 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
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).
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.
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.