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/yonatangross/orchestkitWrote 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/yonatangross/orchestkit/freeze)<a href="https://agentmods.dev/commands/yonatangross/orchestkit/freeze"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/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/yonatangross/orchestkit/freeze"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/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.00064 | $0.00786 |
| Opus 5.5 | $0.00026 | $0.00314 |
| Sonnet 5.5 | $0.00013 | $0.00157 |
| Haiku 4.5 | $0.00006 | $0.00079 |
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 15d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-generated from skills/freeze/SKILL.md
Source: https://github.com/yonatangross/orchestkit
freeze, keep edits inside one directory
State for this session:
!node "skills/freeze/scripts/freeze-guard.mjs" arm "${CLAUDE_PROJECT_DIR}" "${CLAUDE_SESSION_ID}" "$ARGUMENTS"
The line above ran when the skill was invoked: it resolved the argument against the
project dir, followed symlinks, and recorded the real path for this session in
.claude/state/freeze/<session-id>.json. The argument is double-quoted, so a name with
spaces or an apostrophe arrives as typed; a $, backtick or double quote in a dir
name would be interpreted by the shell and is not supported. Report that line to the operator as it reads. If it says NOT changed,
the freeze did not move; say so and stop.
How it works
Invoking this skill also registers a PreToolUse hook on Edit|Write|MultiEdit|NotebookEdit
(the hooks: block above). Claude Code keeps a skill's hooks registered for the rest
of the session, so the fence holds on every later turn. For each edit the hook
resolves where the write would actually land and denies it (exit 2) when that is
outside the frozen dir:
| Target | Verdict |
|---|---|
<frozen>/a.ts, or a new file in a new subdir of <frozen> |
allowed |
<frozen>/../other/b.ts |
denied |
<frozen>-evil/x.ts (a prefix sibling) |
denied |
<frozen>/link/b.ts where link points outside |
denied, symlinks are followed |
<frozen>/dangling.ts, a link to a missing file outside |
denied, the link is chased |
| an edit call with no path | denied |
Usage
/ork:freeze src/hooks # fence edits to src/hooks
/ork:freeze # show the current fence
/ork:freeze off # lift it
Invoking again with another dir moves the fence; a dir that does not exist is refused and the previous fence stays.
When an edit is blocked
The deny reason names the target and the frozen dir. Stop and ask the operator to
widen or lift the freeze. Do not route the change through Bash (sed -i, cat >,
cp) instead: the fence covers the edit tools only, and using Bash to get around it
defeats the reason it was turned on.
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.
- 15d ago First seen · 72 lines · 64 tokens per session scan A 0745126931cc
freeze is a command published in the GitHub repository yonatangross/orchestkit (295 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 786 once invoked, about $0.0003 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-10-02.
Other commands, from other repositories
bug
Reproduce then TDD-fix a ready-for-agent bug ticket in this checkout. Web bugs get a browser repro first.
pn-distill
Remove content, sections, and features that don't earn their place — information architecture reduction. Use when there's too much stuff on the page. For visual decoration reduction, use pn-quieter.
distil-shadow
Decision-equivalence report — did compression preserve your agent's next action?
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.