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 anortham/julie-plugin --skill editinggit clone --depth 1 https://github.com/anortham/julie-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/anortham/julie-plugin/editing)<a href="https://agentmods.dev/skills/anortham/julie-plugin/editing"><img src="https://agentmods.dev/badge/skills/anortham/julie-plugin/editing/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/skills/anortham/julie-plugin/editing"><img src="https://agentmods.dev/badge/skills/anortham/julie-plugin/editing.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.00055 | $0.00733 |
| Opus 5.5 | $0.00022 | $0.00293 |
| Sonnet 5.5 | $0.00011 | $0.00147 |
| Haiku 4.5 | $0.00006 | $0.00073 |
Grade A, and why
editing 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 1mo 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.
This is a copy
100% identical to editing — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Editing Files with Julie
Julie's edit tools change existing files without reading them first. This is the default path for file modifications.
Which tool do I use?
- Creating a new file? Use the Write tool. This skill doesn't apply.
- Changing any text in a file? Use
edit_filewithold_textandnew_text. - Need to understand the file first? Use
get_symbolsfor structure ordeep_divefor full context, then useedit_file. Not Read.
Stop and check
If you catch yourself thinking any of these, you're about to waste tokens:
| Thought | What to do instead |
|---|---|
| "I need to read the file first" | No. edit_file uses DMP fuzzy matching on old_text. It does not need Read. |
| "It's a quick change" | edit_file handles that well. edit_file(old_text=..., new_text=..., dry_run=true) is the fast path. |
| "I'm not sure which symbol I need" | Use fast_search, get_symbols, or deep_dive, then use edit_file. Still no Read + Edit loop. |
| "This isn't a code file" | edit_file works on ANY text file: YAML, TOML, Markdown, .gitignore, configs, everything. |
| "The symbol edit is complex" | Use dry_run=true first. |
Workflow
- Always preview first:
dry_run=true(the default). Review the diff. - Then apply: same call with
dry_run=false.
If a file was only read with offset/limit pagination, treat the view as partial: re-read the whole file before overwriting, or narrow the patch until the match is unambiguous. See references/partial-read-patch-pitfall.md.
edit_file (for any text)
old_text: text to find (DMP fuzzy matched)new_text: replacement textoccurrence:"first"(default),"last", or"all"
Example: the cost of Read + Edit
Changing a version number in Cargo.toml:
Read + Edit pattern (5 calls, ~800 tokens):
- Edit -- fails ("File has not been read yet")
- Read Cargo.toml -- waste
- Grep for the version line -- unnecessary
- Read again with offset -- more waste
- Edit -- finally works
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · -24 lines · -7 tokens per session 2e99040eea9a
- 2mo ago First seen · 87 lines · 62 tokens per session scan A 02ff1685e720
editing is a skill published in the GitHub repository anortham/julie-plugin (2 stars, last pushed 27d ago), licensed MIT. It adds 55 tokens to every session and 733 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to editing, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…