Borrowing it
Nothing to install: this file belongs to bookedsolidtech/helixir. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bookedsolidtech/helixir/main/.claude/commands/freeze.mdgit clone --depth 1 https://github.com/bookedsolidtech/helixirWrote 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/bookedsolidtech/helixir/freeze)<a href="https://agentmods.dev/commands/bookedsolidtech/helixir/freeze"><img src="https://agentmods.dev/badge/commands/bookedsolidtech/helixir/freeze/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/bookedsolidtech/helixir/freeze"><img src="https://agentmods.dev/badge/commands/bookedsolidtech/helixir/freeze.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.00024 | $0.00740 |
| Opus 5.5 | $0.00010 | $0.00296 |
| Sonnet 5.5 | $0.00005 | $0.00148 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
freeze 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/freeze — Activate the Kill Switch
Writes .rea/HALT with a timestamped reason. Once frozen, every REA-governed tool call (native MCP, proxied downstream, and hook-gated) refuses to execute until npx rea unfreeze is run.
Use this when:
- You see the agent doing something unexpected and you want to stop it immediately
- You are handing the session off and want to be sure nothing runs unattended
- A hook or middleware is misbehaving and you need to isolate the problem
- You are about to do something outside the normal governance envelope and want an obvious tripwire
Arguments
$ARGUMENTS(required) — a short reason (one sentence). If empty, prompt the user for one before proceeding. Never freeze without a reason.
Preflight
- Read
.rea/policy.yaml— confirm REA is installed. If missing, report "REA not initialized" and stop. - Check whether
.rea/HALTalready exists. If it does, show the existing reason and ask whether to overwrite.
Step 1 — Validate the reason
- If
$ARGUMENTSis empty or whitespace, prompt: "Reason is required. Describe why you are freezing this session." - If the reason is a placeholder like "test", "asdf", or "freeze", confirm with the user — the reason ends up in the audit log and should be meaningful.
Step 2 — Invoke the freeze CLI
npx rea freeze --reason "$ARGUMENTS"
This command:
- Writes
.rea/HALTwith a JSON payload:{ reason, timestamp, invoker: "slash-command" } - Appends an entry to
.rea/audit.jsonl - Returns exit code 0 on success, non-zero on failure
Step 3 — Confirm
Print the confirmation plainly:
REA session FROZEN
Reason: <reason>
Timestamp: <ISO-8601>
HALT file: .rea/HALT
All governed tool calls are now blocked. To resume: npx rea unfreeze
Behavior under HALT
Once .rea/HALT is present:
- Every hook checks
hooks/_lib/halt-check.shat its top and exits non-zero (blocked) - Every middleware invocation checks
kill-switchfirst and refuses - Slash commands that take actions (not read-only status commands) report FROZEN and refuse to proceed
/reacontinues to work — it is read-only and needs to be able to report the frozen state
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 · 83 lines · 24 tokens per session scan A c5297513139f
freeze is a command published in the GitHub repository bookedsolidtech/helixir (5 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 740 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
ijfw-audit
Run the IJFW audit gate for the current workflow phase. Usage: /ijfw-audit [phase name].
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
_registry-protocol
This protocol is MANDATORY for ALL commands, agents, and phases.
dev-planner
Generate or update DEV-PLAN.md with phased development plan from Product-Spec.md.
learn
Capture what the user changed in a draft the skill wrote, so the loop can learn from it. Every rewrite, cut, or addition is evidence; this command turns it into ledger records that /humanise improve mines for rule-change candidates.
amby.clarify
Resolve the open [NEEDS CLARIFICATION] markers in a feature spec.