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/core-guards)<a href="https://agentmods.dev/plugins/fusengine/agents/core-guards"><img src="https://agentmods.dev/badge/plugins/fusengine/agents/core-guards/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/core-guards"><img src="https://agentmods.dev/badge/plugins/fusengine/agents/core-guards.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
core-guards 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": "core-guards",
"version": "1.1.42",
"description": "Core security guards (git, install, security) and SOLID enforcement hooks for Claude Code",
"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": [
"security",
"guards",
"solid",
"hooks",
"git",
"linter",
"pre-commit"
]
}
What it installs
The manifest is a name and a version. 1 plugin travel with it, and installing the plugin installs all of 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 358a09b7f84d
- 22d ago Changed 661181d785ee
- 1mo ago Changed 803de7091802
- 1mo ago Changed 4724710ab3c3
- 1mo ago First seen · 23 lines scan A 401ff5964b2b
core-guards 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
github
Skills for GitHub pull request workflows — creating PRs, addressing review feedback, and resolving threads.
han-github
Github specific extensions to the Han plugin for agentic planning and coding. Provides skills to post code reviews as PR comments, update a PR description with a consistent format, etc.
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…
pr-voice
Rewrites a thin or empty pull-request description in the repo's own PR voice, measured from its merged history (title convention, length per diff size, recurring headings, issue-closing style). Grounded in the diff; never invents testing claims. Applies with gh pr edit only on explicit confirmation.
gates
Three stateless PreToolUse gates, a PostToolUse JSON-config guard, a 1Password signing nudge, and a docs-consolidation trigger. Denies a git commit that changes code without staging its covering docs (per-plugin README/CLAUDE.md pairs, or the nearest README/CLAUDE/AGENTS walking up); denies a high-fan-out Workflow…