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 skills add LeekJay/claude-skills-plugin --skill claude-code-editorgit clone --depth 1 https://github.com/LeekJay/claude-skills-pluginWrote 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/skills/leekjay/claude-skills-plugin/claude-code-editor)<a href="https://agentmods.dev/skills/leekjay/claude-skills-plugin/claude-code-editor"><img src="https://agentmods.dev/badge/skills/leekjay/claude-skills-plugin/claude-code-editor.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.00042 | $0.02347 |
| Opus 5 | $0.00021 | $0.01174 |
| Sonnet 5 | $0.00008 | $0.00469 |
| Haiku 4.5 | $0.00004 | $0.00235 |
Grade A, and why
claude-code-editor 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 — 347 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Editor Skill
Overview
This skill provides intelligent code editing and refactoring capabilities through a hybrid architecture:
- Skill mode: Use directly in main conversation for simple, focused edits
- Sub-agent mode: Delegate complex, multi-file modifications to isolated context
When to Use This Skill
✅ Use This Skill For:
Large-Scale Refactoring:
- Renaming functions/classes/variables across multiple files
- Restructuring directory layout and moving files
- Changing architectural patterns (e.g., converting class components to hooks)
- Extracting reusable utilities or components
Batch Modifications:
- Applying consistent changes across similar files
- Updating imports after file moves
- Converting code style or patterns project-wide
- Migrating from one library/API to another
Pattern Replacements:
- Replacing deprecated patterns with modern alternatives
- Standardizing error handling approaches
- Converting callback patterns to async/await
- Updating configuration formats
Feature Implementation:
- Implementing features that touch multiple files
- Adding new functionality that requires coordinated changes
- Integrating new libraries across the codebase
❌ Don't Use For:
- Single-file, small edits (use normal editing)
- Quick bug fixes in one location
- Adding simple comments or documentation
- Trivial formatting changes
Decision Framework
Default behavior: For complex editing tasks, prefer Sub-Agent mode unless the task is clearly simple.
🔴 Mandatory Sub-Agent Triggers (ANY ONE triggers delegation)
- Multi-file scope: Task involves 3+ files or mentions "across the project/codebase"
- Refactoring keywords: Description contains refactor, migrate, restructure, reorganize, architecture
- Batch operations: "all files", "every component", "throughout", "project-wide"
- Pattern replacement: Converting patterns, updating API usage, library migration
- Structural changes: Moving files, renaming directories, changing folder structure
- Feature implementation: New feature touching multiple modules/layers
- Import chain effects: Changes that will cascade through import dependencies
- Unknown scope: Cannot immediately determine how many files are affected
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 · 347 lines · 42 tokens per session scan A 6ef308603f72
claude-code-editor is a skill published in the GitHub repository LeekJay/claude-skills-plugin (4 stars, last pushed 8mo ago), licensed MIT. It adds 42 tokens to every session and 2,347 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…