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 a554b554/Reactant --skill editgit clone --depth 1 https://github.com/a554b554/ReactantWrote 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/a554b554/reactant/edit)<a href="https://agentmods.dev/skills/a554b554/reactant/edit"><img src="https://agentmods.dev/badge/skills/a554b554/reactant/edit/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/a554b554/reactant/edit"><img src="https://agentmods.dev/badge/skills/a554b554/reactant/edit.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.00038 | $0.00662 |
| Opus 5.5 | $0.00015 | $0.00265 |
| Sonnet 5.5 | $0.00008 | $0.00132 |
| Haiku 4.5 | $0.00004 | $0.00066 |
Grade A, and why
edit 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Edit
Activation Boundary
This is a tag-only worker skill. Use it only after execute or execute-one
selects an exact <@edit...> annotation in a target document and hands off its
context. Never activate it from an ordinary chat-window editing request,
semantic similarity, or any skill other than those two routers. Without that
router handoff, do not edit anything; tell the user to place an <@edit> tag in
the document and run execute or execute-one.
Apply the edit described in the prompt to the surrounding block, then consume the tag.
Tag
<@edit: instruction>
Examples: <@edit: make this shorter>, <@edit: rewrite in formal tone>,
<@edit: revise to align with ``intro.md``>.
Input
- File path — the document being processed.
- Surrounding block — the maximal run of non-blank lines containing the tag; blank lines bound it. Read the full file when broader context helps.
- Prompt — what to change.
- Modifiers and context references — see below.
Workflow
- Read the surrounding block; read the full file if you need broader context.
- Resolve any context references in the prompt.
- Apply the requested edit to the block's authored prose.
- Write the result back to the file: replace the surrounding block (including
the
<@edit: ...>tag) with the edited text.
Scope Modifiers
- Protect
<< >>— text inside must NOT be modified. Preserve it exactly; remove the<<>>delimiters in the output. - Field
(( ))— ONLY text inside may be modified; everything else in the block is context. Remove the(())delimiters in the output. - Neither present: the whole surrounding block is editable.
Context References
Double-backtick references in the prompt point to external resources.
- As input: read the referenced file or section for context.
- As output: write the requested content to the referenced destination (a path is resolved relative to the document's directory unless absolute).
- Remove the reference and its delimiters from the document output.
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 · +25 lines · +24 tokens per session c89b48a5648a
- 1mo ago First seen · 48 lines · 14 tokens per session scan A ea13bfbcaa2b
edit is a skill published in the GitHub repository a554b554/Reactant (54 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 662 once invoked, about $0.0002 per session on Opus 5.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 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…
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…