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/commands/sirsjg/flux/flux-status)<a href="https://agentmods.dev/commands/sirsjg/flux/flux-status"><img src="https://agentmods.dev/badge/commands/sirsjg/flux/flux-status/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/commands/sirsjg/flux/flux-status"><img src="https://agentmods.dev/badge/commands/sirsjg/flux/flux-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00011 | $0.00273 |
| Opus 5.5 | $0.00004 | $0.00109 |
| Sonnet 5.5 | $0.00002 | $0.00055 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade A, and why
flux-status 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
Flux Status
Show the current state of your Flux board and suggest what to work on next.
Instructions
-
Use
list_projectsto get all projects with their stats. -
For the active project (or most recently updated), use
list_epicsandlist_tasksto get the full picture. -
Present a summary:
- Tasks in progress (doing)
- Blocked tasks and what's blocking them
- Tasks ready to start (todo with no blockers)
- Recently completed tasks
-
Suggest the next task to pick up based on:
- Unblocking other tasks (high impact)
- No dependencies (ready to start)
- Epic progress (finishing an epic)
Output Format
📊 Project: my-app
🔄 In Progress (2)
• Implement JWT service
• Design dashboard layout
🚫 Blocked (1)
• Create login endpoint (waiting on: JWT service)
✅ Ready to Start (3)
• Set up CI pipeline
• Write API documentation
• Add unit tests for auth
💡 Suggested Next: "Set up CI pipeline" - unblocks deployment tasks
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 · 46 lines · 11 tokens per session scan A d20fd0fdd03b
flux-status is a command published in the GitHub repository sirsjg/flux (105 stars, last pushed 5d ago), licensed MIT. It adds 11 tokens to every session and 273 once invoked, about $0.0000 per session on Opus 5.5. 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 commands, from other repositories
deliver
Verify, push, measure, and deliver the current OverClick card.
board
Show the actionable OverClick queue and this session's active claims.
claim
Claim an OverClick card and load its execution briefing.
card
Open one self-contained OverClick card.
arrange-workspace-flow
Workflow for arranging a workspace: layout, reference source code, business/technical context, ecosystem setup.
tracker-sync
Project a flow spec to a tracker (Linear/GitHub/GitLab/Jira) and reconcile body/status/comments two-way — projection, not coordination. NOT plan-sync (/flow-next:sync).