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 skill-generatorgit 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/skill-generator)<a href="https://agentmods.dev/skills/a554b554/reactant/skill-generator"><img src="https://agentmods.dev/badge/skills/a554b554/reactant/skill-generator/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/skill-generator"><img src="https://agentmods.dev/badge/skills/a554b554/reactant/skill-generator.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.00049 | $0.00737 |
| Opus 5.5 | $0.00020 | $0.00295 |
| Sonnet 5.5 | $0.00010 | $0.00147 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
skill-generator 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.
Skill Generator
Entry Boundary
This is a direct entry skill, alongside execute and execute-one. It is not
a Reactant tag skill or document router. Activate it only from an explicit
user request to create a Reactant project-local skill, such as:
/skill-generator a translate skill that preserves citations and LaTeX commands
There is no inline form for this entry skill. execute and execute-one must
never select or dispatch an apparent generator annotation in an authored
document. Do not read, consume, or edit a document merely to obtain the
generator request.
The generated directory is a standard Agent Skill. The router agent discovers the new worker by reading project skill roots on its next invocation; there is no registry and no programmatic tag scanner.
Input
Accept the user's direct natural-language description of the new skill and the current project root. If the intended behavior, name, or file effects are materially ambiguous, clarify them before creating files.
Workflow
- Read the description and
references/skill-contract.mdin this skill directory. Infer the requested behavior without reducing the description to a machine tag grammar. - Choose a name made of lowercase letters or numbers separated by single
hyphens. It must not be a reserved name (
execute,execute-one,skill-generator,chat-user,resolve,chat-model,comment) or collide with another skill unless the user explicitly requests an allowed override. - Inspect the project-local skill root and create
.reactant/skills/if it does not exist. - Write
.reactant/skills/<name>/SKILL.mdaccording to the contract: YAML frontmatter with a matchingname, a description explicitly limiting activation to router-dispatched tags, anActivation Boundarysection, tag examples, input behavior, workflow, scope-modifier and context-reference handling, consumption behavior, and clean failure behavior. Add supportingscripts/,references/, or assets only when the skill needs them; keep the skill self-contained. - Validate the directory by reading it against the structural contract: frontmatter, naming, required behavior, self-containment, and reserved-name rules. If an optional structural Agent Skills or Reactant validator is available, it may be run as an additional check. Such a validator must not scan authored documents or classify annotations.
- Fix any structural errors and validate again. If the skill cannot be made valid, remove only the incomplete directory created by this invocation and report the diagnostics.
- Report the created path and the generated worker's annotation form. Do not modify an authored document as part of generation.
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 First seen · 73 lines · 49 tokens per session scan A a9c2c3a47858
skill-generator is a skill published in the GitHub repository a554b554/Reactant (54 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 737 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-09-10.
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…