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 skills/a554b554/reactant/plannpx skills add a554b554/Reactant --skill plangit clone --depth 1 https://github.com/a554b554/ReactantWhat 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.00021 | $0.00791 |
| Opus 5 | $0.00010 | $0.00396 |
| Sonnet 5 | $0.00004 | $0.00158 |
| Haiku 4.5 | $0.00002 | $0.00079 |
Grade A, and why
plan 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 2d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan
Analyze the surrounding text and return a structured revision plan. Supports multi-turn conversation where the user can refine the plan iteratively before resolving.
Input
- File path: the file being processed.
- Surrounding text: the paragraph or block where the
<@plan: ...>tag appears, including any prior<@plan>/<@output>pairs in the chain. - Prompt: the revision goal (e.g., "how to make this better", "restructure for clarity").
Workflow
- Read the surrounding text. Optionally read the full file for broader context.
- Check for prior
<@plan>/<@output>pairs in the tag chain. If they exist, treat them as conversation history. - Analyze the text against the revision goal, incorporating any conversation history.
- Write the result back to the file: insert your plan as a
<@output: ...>tag immediately after the current<@plan>tag. The format must be exactly:<@output: your plan here>do NOT use a closing</@output>tag, and do NOT place content outside the tag. Keep the original content and all<@plan>/<@output>tags intact.
Multi-Turn Conversation
After receiving an <@output>, the user may:
- Edit the
<@output>directly — modify the plan text, then use<@resolve>to apply it. - Add another
<@plan:>tag after the<@output>— this continues the conversation. The new<@plan>prompt is treated as a follow-up that can refine, extend, or redirect the previous plan.
Each <@plan>/<@output> pair forms one turn. When producing a new <@output>, read the full chain of prior turns as conversation history. All prior pairs stay intact — only append a new <@output> after the latest <@plan>. The output plan should always be included in the <@output> tag, e.g., <@output: your plan here>. The conversation chain is terminated by <@resolve>, which consumes the entire chain.
Scope Modifiers
The surrounding text may contain scope modifier tags. When producing a plan, take these into account:
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.
- 2d ago First seen · 49 lines · 21 tokens per session scan A fcedbe8e631f
plan is a skill published in the GitHub repository a554b554/Reactant (54 stars, last pushed 29d ago), licensed MIT. It adds 21 tokens to every session and 791 once invoked, about $0.0001 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-30.
Other skills, from other repositories
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…