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.
git clone --depth 1 https://github.com/fusengine/agentsWrote 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/plugins/fusengine/agents/react-expert)<a href="https://agentmods.dev/plugins/fusengine/agents/react-expert"><img src="https://agentmods.dev/badge/plugins/fusengine/agents/react-expert/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/plugins/fusengine/agents/react-expert"><img src="https://agentmods.dev/badge/plugins/fusengine/agents/react-expert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
fuse-react 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 7d 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.
What it actually says
{
"name": "fuse-react",
"version": "1.0.24",
"description": "Expert React 19 with hooks, TanStack Router, TanStack Form, Zustand, Testing Library, shadcn/ui, and SOLID principles",
"author": {
"name": "Fusengine",
"email": "[email protected]",
"url": "https://github.com/fusengine"
},
"homepage": "https://github.com/fusengine/agents",
"repository": "https://github.com/fusengine/agents",
"license": "MIT",
"keywords": [
"react",
"react-19",
"hooks",
"tanstack-router",
"zustand",
"shadcn",
"testing-library",
"solid"
]
}
What it installs
The manifest is a name and a version. 8 skills, 1 agent travel with it, and installing the plugin installs all of them — 329 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 7d ago Changed a4e2a82d908f
- 21d ago Changed 403a70f63bdf
- 22d ago Changed d51dad704e44
- 25d ago Changed a428cfc7096e
- 1mo ago Changed ce7e1061b924
- 1mo ago Changed 26cb412f2092
- 1mo ago First seen · 24 lines scan A dda12113883d
fuse-react is a plugin published in the GitHub repository fusengine/agents (33 stars, last pushed 7d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-03.
Other plugins, from other repositories
rageatc-code-oss
Scale-adaptive software development — TDD, verification, perspective-based review, interface design, and tool capabilities (browser automation, PDFs, YouTube transcripts, local-LLM and Codex delegation).
r-lib
Collection of skills for R package developers.
mean-tester
Mean tests another agent through readonly probes or marked actions on admitted test installations, checks owned approvals and state, and reports a computed ship verdict. It files nothing and fixes nothing.
jig
Spec-driven, review-enforced, hook-gated AI-native development workflow for Claude Code.
agentic-validation-skills
Agentic test automation guidelines based on the CIGE standard (Context, Intent, Guardrails, Execution) for authoring self-healing, goal-driven AI test cases.
frontend
Use when adding or changing a feature, page, API call, hook, form, or component in a React or Next.js app laid out as infrastructure + domain + view + routes; when deciding which layer code belongs in; when reviewing a diff for layering violations; or when structuring a greenfield frontend. Covers dependency rules…