Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/CES-Ltd/Luminpx agentmods add commands/ces-ltd/lumi/octo-freezeWrote 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/ces-ltd/lumi/octo-freeze)<a href="https://agentmods.dev/commands/ces-ltd/lumi/octo-freeze"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-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/ces-ltd/lumi/octo-freeze"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-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.00009 | $0.00442 |
| Opus 5 | $0.00005 | $0.00221 |
| Sonnet 5 | $0.00002 | $0.00088 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
octo-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 12d 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.
This is a copy
89% identical to octo-freeze — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Freeze Mode - Edit Boundary Enforcement
Instructions
When the user invokes /octo:freeze <directory>, activate freeze mode to restrict Edit and Write operations to the specified directory.
Activation
- Resolve the directory argument to an absolute path
- Ensure trailing
/for safe prefix matching - Write the boundary to the state file:
# Resolve to absolute path
freeze_dir="$(cd "$1" 2>/dev/null && pwd)" || freeze_dir="$1"
# Write state
echo "${freeze_dir}" > "/tmp/octopus-freeze-${CLAUDE_SESSION_ID:-$$}.txt"
What It Does
Freeze mode adds a PreToolUse safety net on Edit and Write tools. Any file operation targeting a path outside the frozen directory is blocked with a deny decision. This prevents accidental edits to unrelated code.
Blocked: Edit, Write to files outside the boundary Unaffected: Read, Bash, Glob, Grep (investigation stays unrestricted)
Usage
/octo:freeze src/auth
/octo:freeze ./packages/core
/octo:freeze /absolute/path/to/module
After activation, confirm to the user:
🔒 Freeze mode activated. Edits restricted to: <resolved-path>
Read/search operations remain unrestricted.
Use /octo:unfreeze to remove this restriction.
Argument Required
If invoked without a directory argument, ask the user which directory to freeze:
Which directory should I restrict edits to? Example: /octo:freeze src/auth
When to Use
- Debugging a specific module (auto-activated by skill-debug)
- Code review where you want to ensure no unrelated changes
- Focused refactoring within a single package
- Any time you want to guarantee edit boundaries
See Also
/octo:careful— Warn before destructive commands/octo:guard— Activate both careful + freeze together/octo:unfreeze— Remove freeze restriction
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.
- 12d ago First seen · 67 lines · 9 tokens per session scan A 93b8cdfd5e7a
octo-freeze is a command published in the GitHub repository CES-Ltd/Lumi (31 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 442 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to octo-freeze, differing in 6 lines, and is treated as a copy.
Other commands, from other repositories
refactor-clean
You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
workflow-classify
Classify task size (S/M/L/XL) and recommend the appropriate workflow pipeline.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
sonarqube
Analyze SonarCloud quality issues for a specific PR.
plan-start
5-phase planning command: PRD analysis, design review, technical decisions, dynamic research team, metrics. Produces a complete implementation plan + ADRs before any code is written.