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/sirsjg/fluxWrote 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/sirsjg/flux/plugin)<a href="https://agentmods.dev/plugins/sirsjg/flux/plugin"><img src="https://agentmods.dev/badge/plugins/sirsjg/flux/plugin/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/sirsjg/flux/plugin"><img src="https://agentmods.dev/badge/plugins/sirsjg/flux/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
flux 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 1mo 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": "flux",
"description": "Generate epics and tasks in Flux from project requirements. Ship with less chaos.",
"version": "1.0.0",
"author": {
"name": "sirsjg"
},
"repository": "https://github.com/sirsjg/flux"
}
What it installs
The manifest is a name and a version. 3 commands, 1 MCP server travel with it, and installing the plugin installs all of them — 32 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.
- 1mo ago First seen · 10 lines scan A 948fb0736ef4
flux is a plugin published in the GitHub repository sirsjg/flux (104 stars, last pushed 1mo 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-08-30.
Other plugins, from other repositories
chorus
Chorus AI-DLC collaboration platform plugin for Claude Code. Automates session lifecycle, provides MCP tools for PM/Developer/Admin workflows, and enables multi-agent team observability.
overclick
Claim, execute, and deliver cards on your own self-hosted OverClick board. Ships the workflow skill, the /overclick: commands, and hooks: a session-start board snapshot and a delivery commit check run by default, while the claim guard and the stop/harness guards ship disabled. The only network endpoint is the OverClic.
ticket-flow
Beads-backed ticket workflow for Claude Code: spec → pickup → implement → finish behind verdict and merge gates, orchestrated by /flow (--local with resume, --parallel, --serial/--loop unattended queue runner), each ticket in its own git worktree. Five visible commands; the phase skills are model-invoked.
taskwarrior
Token-dense recipes for taskwarrior CLI: dense listings, single-field lookups, batched exports, full-text search.
claude-orchestration
Parallel multi-agent orchestration for complex features with Task-based coordination and git-wt --stack worktree isolation.
pf-workflow
Spec-driven workflow toolkit for multi-agent CLI development: task packets, journal, retro, autopilot.