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 chat-usergit 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/chat-user)<a href="https://agentmods.dev/skills/a554b554/reactant/chat-user"><img src="https://agentmods.dev/badge/skills/a554b554/reactant/chat-user/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/chat-user"><img src="https://agentmods.dev/badge/skills/a554b554/reactant/chat-user.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.00744 |
| Opus 5.5 | $0.00015 | $0.00298 |
| Sonnet 5.5 | $0.00008 | $0.00149 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
chat-user 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chat User
Activation Boundary
This is a tag-only worker skill, not the host's normal chat interface. Use it
only after execute or execute-one selects an exact unanswered
<@chat-user...> annotation and hands off its document chain. Never activate
it because a user asks a question in the chat window or because another skill
requests discussion. Without router handoff, append nothing.
Answer the user's document-local chat turn. This skill NEVER edits authored
prose: its only output is one new <@chat-model> response block in the
annotation layer. Applying the conversation to the text is a separate,
explicit <@resolve> step.
Tags
The user writes a chat turn:
<@chat-user: question or request about the preceding text>
This skill replies with a paired block whose markers each occupy their own line:
<@chat-model name="exact-model-identifier-or-unknown">
multiline response
</@chat-model>
A chain may hold many turns: chat-user, chat-model, chat-user,
chat-model, ... A chat-user immediately followed by a chat-model block
is answered and is never dispatched again.
Input
- File path — the document being processed.
- The unanswered
<@chat-user>tag — the turn to answer. - Chain history — all earlier
chat-user/chat-modelturns in this chain, in order. Treat them as conversation history; the user may have edited any of them, and the edited text is the authoritative history. - Preceding authored block — the text the chain discusses. Read the full file for broader context when useful.
Workflow
- Read the preceding authored block, the full chain history, and the new turn's prompt. Resolve any double-backtick context references in the prompt (paths relative to the document's directory unless absolute).
- Compose a response: a plan, critique, answer, or proposal, as the turn
requests. Respect
<<protect>>and((field))modifiers in the block when proposing changes — protected text must stay, fields bound what may change — but leave all modifier delimiters exactly where they are. - Insert exactly one response block immediately after the unanswered
<@chat-user>tag's line:- Opener:
<@chat-model name="...">on its own line, wherenameis the exact model identifier your host exposes, orunknown— never a guess. - Response text on the following lines. If any response line would consist
exactly of
</@chat-model>, escape it as\</@chat-model>. - Closer:
</@chat-model>on its own line.
- Opener:
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 · 78 lines · 38 tokens per session scan A 1adb5aaf6aa3
chat-user 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 744 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…