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/claude-rules)<a href="https://agentmods.dev/plugins/fusengine/agents/claude-rules"><img src="https://agentmods.dev/badge/plugins/fusengine/agents/claude-rules/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/claude-rules"><img src="https://agentmods.dev/badge/plugins/fusengine/agents/claude-rules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
fuse-rules 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-rules",
"version": "1.0.26",
"description": "Global rules for all Claude Code sessions: APEX workflow, SOLID/DRY enforcement, project detection, agent delegation, frontend/git standards",
"author": {
"name": "Fusengine",
"url": "https://github.com/fusengine"
},
"homepage": "https://github.com/fusengine/agents",
"repository": "https://github.com/fusengine/agents",
"license": "MIT"
}
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 cd2dd3eda3e1
- 22d ago Changed c5ff13513e37
- 1mo ago Changed 511e5d79958d
- 1mo ago Changed 3e226db6d74d
- 1mo ago First seen · 13 lines scan A b55643da0ab7
fuse-rules 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
open-source
Collection of skills for open-source R and Python package developers.
dark-factory
Curie's default dark factory agent: one labelled GitHub issue in, one reviewed pull request or one stated reason out. One agent reads the issue through the platform's getissue tool, pins acceptance criteria, plans, gets the plan reviewed by an Opus plan-reviewer subagent, writes a failing test where feasible, implemen.
github-activity
Read-only GitHub activity reporter for program managers. One hosted connector reads merged pull requests, opened and closed issues, and milestone movement across several repositories since a point in time. It holds no write tool, the tool policy allows only the read tool so anything else fails closed, and the…
radin
Cost-optimized agentic workflow stack for solo devs: backlog orchestration (radin-batch, radin-plan, radin-review) plus curated companion tools.
agile-ledger
Plain-Markdown Scrum/Agile product management for Claude Code — backlog, sprints, board, velocity, releases, and GitHub traceability from slash commands. The ledger lives in its own repo, one folder per project, so code repos stay clean.
claude-phases
Break work into phases and let a Claude Code session build them one PR at a time, steered from anywhere.