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/forkflux/forkfluxWrote 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/forkflux/forkflux/ff-reopen-context)<a href="https://agentmods.dev/commands/forkflux/forkflux/ff-reopen-context"><img src="https://agentmods.dev/badge/commands/forkflux/forkflux/ff-reopen-context/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/forkflux/forkflux/ff-reopen-context"><img src="https://agentmods.dev/badge/commands/forkflux/forkflux/ff-reopen-context.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.00021 | $0.00176 |
| Opus 5.5 | $0.00008 | $0.00070 |
| Sonnet 5.5 | $0.00004 | $0.00035 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
ff-reopen-context 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 2mo 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-reopen-context
Description
Retrieves focused metadata for a retry iteration, including the rejection reason, original job ID, retry counters, summary, and constraints. It intentionally avoids returning the original full context payload.
Required MCP tool
forkflux_get_reopen_context
Agent instructions
- Verify the supplied
job_ididentifies a retry iteration, not the original completed job. - Call
forkflux_get_reopen_contextwith the job ID. - Use the returned rejection metadata to prepare the retry execution.
- If the tool fails, report the exact error and stop.
Output
Summarize the rejection reason, original job ID, retry count, and constraints. 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.
- 2mo ago First seen · 25 lines · 21 tokens per session scan A 4d4e1822ef9d
ff-reopen-context is a command published in the GitHub repository forkflux/forkflux (6 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 176 once invoked, about $0.0001 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-31.
Other commands, from other repositories
fix
A code-repair command that detects and fixes errors reported by language servers, linters, or type checkers. These tools find code problems such as invalid syntax, style issues, and mismatched data types.
clean
A command for finding code that is no longer used and removing it after checking that tests still pass.
self-healing
Automatically detect and recover from errors without interrupting your flow.
deep-audit.skeleton
Description: This section is populated by Bootstrap with manifest data. Required manifest fields: project.description, stack.primary, project.structure, project.subprojects, stack.orm, stack.authmethod Example output.
toh-fix
Evidence-first debugging — find the root cause with proof before touching code.
bug
Report a bug from a plain description — triggers investigation, structured documentation and fix coordination.