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/forkflux/forkflux/ff-updategit clone --depth 1 https://github.com/forkflux/forkfluxWhat 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 | $0.00021 | $0.00220 |
| Opus 5 | $0.00010 | $0.00110 |
| Sonnet 5 | $0.00004 | $0.00044 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
ff-update 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 2d 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
ff-update
Description
Updates a published job's context_payload and/or constraints when the handoff needs clarification or correction. It does not change the job's summary, target role, priority, ownership, dependencies, or lifecycle state.
Required MCP tool
forkflux_update_job
Agent instructions
- Verify a valid
job_idand identify at least one field to replace. - Pass
context_payloadas a structured JSON object, not a flat string. - Pass
constraintsas an array of concrete acceptance criteria when updating them. - Do not use this command to change the target role, objective, priority, ownership, or status.
- Call
forkflux_update_jobwith the validated arguments. - If the tool fails, report the exact error and stop.
Output
Report the updated job_id, the fields changed, and a concise summary. Do not dump raw JSON.
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.
- 2d ago First seen · 27 lines · 21 tokens per session scan A 2e350148aa3b
ff-update is a command published in the GitHub repository forkflux/forkflux (6 stars, last pushed 21d ago), licensed Apache-2.0. It adds 21 tokens to every session and 220 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-31.
Other commands, from other repositories
project
Generate project documentation (product.md, structure.md, tech.md, codemaps/).
toh-help
Display all Toh Framework commands and quick usage guide.
feature
Create a feature specification using spec-driven development.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
speckit.opsmill.retrospect
Run a session retrospective that surfaces context-management gaps and routes them to approved follow-up actions.
create-issue
Transform feature descriptions, bug reports, or improvement ideas into well-structured GitHub issues.