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/stat-guy/text-editor/claude-mdgit clone --depth 1 https://github.com/stat-guy/text-editorWhat 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.01598 | $0.01598 |
| Opus 5 | $0.00799 | $0.00799 |
| Sonnet 5 | $0.00320 | $0.00320 |
| Haiku 4.5 | $0.00160 | $0.00160 |
Grade A, and why
text-editor 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 yesterday.
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 — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Implementation Guide
This guide shows you how to set up and use the Advanced MCP Text Editor Server with Claude Desktop and Claude Code CLI.
Quick Setup for Claude Desktop
1. Install and Build
# Clone the repository
git clone https://github.com/stat-guy/text-editor.git
cd text-editor
# Install dependencies and build
npm install
npm run build
2. Configure Claude Desktop
Open your Claude Desktop configuration file:
macOS/Linux:
code ~/Library/Application\ Support/Claude/claude_desktop_config.json
Windows:
code %APPDATA%\Claude\claude_desktop_config.json
Add the text-editor server:
{
"mcpServers": {
"text-editor": {
"command": "node",
"args": ["/ABSOLUTE/PATH/TO/text-editor/dist/index.js"]
}
}
}
⚠️ Important:
- Use absolute paths (not relative)
- Point to
dist/index.js(notsrc/index.ts) - Replace
/ABSOLUTE/PATH/TO/with your actual path
3. Restart Claude Desktop
Completely quit and restart Claude Desktop for the changes to take effect.
4. Verify Installation
Look for the "Search and tools" icon (🔍) in Claude Desktop. You should see these 6 tools available:
view- View files and directoriesstr_replace- Replace text in filescreate- Create new filesinsert- Insert text at specific linesundo_edit- Revert changesfile_info- Get file metadata
Quick Setup for Claude Code CLI
1. Add to Local Configuration
# Navigate to your project directory
cd /path/to/your/project
# Add the text-editor MCP server
claude mcp add text-editor node /ABSOLUTE/PATH/TO/text-editor/dist/index.js
# Verify it's connected
claude mcp list
You should see:
text-editor: node /ABSOLUTE/PATH/TO/text-editor/dist/index.js - ✓ Connected
2. Start Using
You can now use text editing commands in Claude Code:
# Start Claude Code in your project
claude code
# Example usage in Claude conversation:
# "Please view the package.json file"
# "Replace 'debug: false' with 'debug: true' in config.js"
# "Create a new file called utils.ts with basic utility functions"
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.
- yesterday First seen · 288 lines · 1,598 tokens per session scan A 0d7f9219caf4
text-editor CLAUDE.md is an instructions file published in the GitHub repository stat-guy/text-editor (0 stars, last pushed 11mo ago), licensed MIT. It adds 1,598 tokens to every session, about $0.0080 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-01.
Other instructions, from other repositories
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.