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-add)<a href="https://agentmods.dev/commands/sirsjg/flux/flux-add"><img src="https://agentmods.dev/badge/commands/sirsjg/flux/flux-add.svg" alt="Measured on agentmods" 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.00253 |
| Opus 5 | $0.00005 | $0.00127 |
| Sonnet 5 | $0.00002 | $0.00051 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
flux-add 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
Flux Add
Quickly create a task in Flux from a brief description.
Instructions
-
Parse the user's input to extract:
- Task title (required)
- Epic or project context (if mentioned)
- Any notes or acceptance criteria
-
If no project is specified, use
list_projectsto find the most recently updated project or ask which to use. -
If an epic is mentioned by name, use
list_epicsto find the matching epic ID. -
Create the task with
create_taskincluding:- A clear, actionable title
- Any provided notes
- Epic association if specified
-
Confirm creation with the task title and location.
Examples
User: "add task: implement password reset flow" → Creates task "Implement password reset flow" in the active project
User: "flux add: fix the login bug in the auth epic" → Creates task "Fix login bug" in the Authentication epic
User: "add a task to review the API documentation with high priority" → Creates task "Review API documentation" with priority note
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 First seen · 38 lines · 11 tokens per session scan A c6849fdbbc9f
flux-add is a command published in the GitHub repository sirsjg/flux (100 stars, last pushed 10d ago), licensed MIT. It adds 11 tokens to every session and 253 once invoked, about $0.0001 per session on Opus 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.
claim
Claim an OverClick card and load its execution briefing.
board
Show the actionable OverClick queue and this token's active claims.
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).