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/statusline-mod)<a href="https://agentmods.dev/plugins/fusengine/agents/statusline-mod"><img src="https://agentmods.dev/badge/plugins/fusengine/agents/statusline-mod/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/statusline-mod"><img src="https://agentmods.dev/badge/plugins/fusengine/agents/statusline-mod.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
fuse-statusline 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 6d 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-statusline",
"version": "1.0.15",
"description": "Responsive statusline mod for Claude Code (function hooks, no command hooks); figures computed by the core-guards statusline engine",
"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",
"types": "./types/index.d.ts",
"keywords": ["statusline", "mod", "hooks"]
}
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.
- 6d ago First seen · 16 lines scan A d1f5759bbf84
fuse-statusline is a plugin published in the GitHub repository fusengine/agents (32 stars, last pushed 6d 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-10-13.
Other plugins, from other repositories
i-have-adhd
Shape Gemini CLI output for an ADHD reader: lead with the next action, number steps, suppress tangents, restate state, make wins visible.
customer-experience
Support operations, escalation management, voice of customer, and self-service. Owns what the customer experiences after the sale.
accounting
Eight-phase accounting cycle — analyze, journal, ledger, trial balance, adjust, statements, close with 5 utility skills.
the-44-percent-rule
The 44% Rule — Find 44% more AI use cases in your business. A Claude Code plugin based on Kim, Kim & Koning (2026) field experiment of 515 startups: businesses shown how others reorganize around AI find 44% more use cases, 1.9x higher revenue, and 18% more likely to acquire paying customers. Automates the 'showing' so.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.