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.
/plugin marketplace add fusengine/agentsnpx agentmods add plugins/fusengine/agents/core-guardsgit 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.svg" alt="Measured on agentmods" 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 today.
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.37",
"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 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.
- today Changed 4724710ab3c3
- yesterday First seen · 23 lines scan A 401ff5964b2b
core-guards is a plugin published in the GitHub repository fusengine/agents (25 stars, last pushed today), 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
gates
Four stateless PreToolUse gates, a PostToolUse JSON-config guard, 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); asks before a new-project scaffold command (npm create vite…
dootask
DooTask 插件开发与编码协作工具集：脚手架、发布、CLAUDE.md 优化与 Conventional Commits 提交.
accessibility
WCAG-EM accessibility audit workflow — scope, evaluate, report, remediate, retest with conformance scoring.
accounting
Eight-phase accounting cycle — analyze, journal, ledger, trial balance, adjust, statements, close with 5 utility skills.
compliance
GRC Compliance Lifecycle — scope, assess, remediate, certify, monitor with 48 skills across 30+ regulations.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.