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.
npx agentmods add commands/sirsjg/flux/flux-generategit 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-generate)<a href="https://agentmods.dev/commands/sirsjg/flux/flux-generate"><img src="https://agentmods.dev/badge/commands/sirsjg/flux/flux-generate.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.00010 | $0.00279 |
| Opus 5 | $0.00005 | $0.00139 |
| Sonnet 5 | $0.00002 | $0.00056 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
flux-generate 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
Flux Generate
Analyze the current project and generate a structured breakdown of epics and tasks in Flux.
Process
-
Gather Requirements: Read README.md, PRD documents, specs, or any files the user specifies. If none exist, ask the user to describe what they're building.
-
Identify the Project: Check if a Flux project exists for this codebase using
list_projects. If not, create one withcreate_project. -
Define Epics: Break down the requirements into major features or workstreams. Each epic should represent a distinct deliverable. Create them with
create_epic. -
Create Tasks: For each epic, create granular tasks that can be completed in a single work session. Include:
- Clear, actionable titles
- Detailed notes with acceptance criteria
- Dependencies on other tasks where applicable
-
Set Dependencies: Identify task dependencies (e.g., "API endpoint" must be done before "Frontend integration") and set them using the
depends_onfield.
Output
After generation, summarize what was created:
- Project name
- Number of epics and tasks
- Key dependencies identified
- Suggested starting point (tasks with no blockers)
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 · 31 lines · 10 tokens per session scan A b03a992ef2dd
flux-generate is a command published in the GitHub repository sirsjg/flux (100 stars, last pushed 9d ago), licensed MIT. It adds 10 tokens to every session and 279 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).