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 phgit 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/ph)<a href="https://agentmods.dev/skills/a554b554/reactant/ph"><img src="https://agentmods.dev/badge/skills/a554b554/reactant/ph/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/ph"><img src="https://agentmods.dev/badge/skills/a554b554/reactant/ph.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.00037 | $0.00549 |
| Opus 5.5 | $0.00015 | $0.00220 |
| Sonnet 5.5 | $0.00007 | $0.00110 |
| Haiku 4.5 | $0.00004 | $0.00055 |
Grade A, and why
ph 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Placeholder
Activation Boundary
This is a tag-only worker skill. Use it only after execute or execute-one
selects an exact <@ph...> annotation in a target document and hands off its
context. Never activate it from ordinary chat, semantic similarity, or any
skill other than those two routers. Without that handoff, produce no
placeholder and direct the user to add the tag and run a router.
Generate content that fits naturally at the tag position and replace only the tag with it.
Tag
<@ph>
<@ph: hint about what to fill>
Example: We evaluated <@ph: the number of participants> participants.
Input
- File path — the document being processed.
- Surrounding block — the maximal run of non-blank lines containing the tag; blank lines bound it.
- Prompt (optional) — a hint (for example "a transition sentence"). Default: infer from context.
Workflow
- Read the text before and after the tag; read the full file if broader context helps.
- Generate content that fits naturally at that exact position in tone, style, and meaning.
- Write the result back: replace ONLY the
<@ph>tag with the generated text. All surrounding text stays untouched.
Scope Modifiers
<@ph> never modifies surrounding content, so modifiers mainly provide
context:
- Protect
<< >>— context only; never modify. This skill does not remove protect delimiters outside its own insertion. - Field
(( ))— when the tag sits inside a field, generate content that belongs in that field.
Context References
Double-backtick references in the prompt point to resources that inform the
generated content (for example <@ph: a summary based on ``results.md``>).
Resolve paths relative to the document's directory unless absolute.
Rules
- The output must read as if it had always been part of the text; keep it concise and contextually appropriate.
- Replace only the selected annotation. Preserve every unrelated annotation,
<@comment: ...>tag,<@chat-model>block, and contextual literal/example byte-for-byte. - On any error (for example an unreadable referenced file), fail cleanly: leave the tag, change nothing, report.
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 · +26 lines · +23 tokens per session d0c8054bc661
- 1mo ago First seen · 44 lines · 14 tokens per session scan A 0d2ea1b56ae5
ph is a skill published in the GitHub repository a554b554/Reactant (54 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 549 once invoked, about $0.0001 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…