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/tmusser/ai-engineering-skillsnpx agentmods add skills/tmusser/ai-engineering-skills/scope-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/skills/tmusser/ai-engineering-skills/scope-freeze)<a href="https://agentmods.dev/skills/tmusser/ai-engineering-skills/scope-freeze"><img src="https://agentmods.dev/badge/skills/tmusser/ai-engineering-skills/scope-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/skills/tmusser/ai-engineering-skills/scope-freeze"><img src="https://agentmods.dev/badge/skills/tmusser/ai-engineering-skills/scope-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.00016 | $0.00985 |
| Opus 5.5 | $0.00006 | $0.00394 |
| Sonnet 5.5 | $0.00003 | $0.00197 |
| Haiku 4.5 | $0.00002 | $0.00098 |
Grade A, and why
scope-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 17d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scope Freeze
Purpose
Prevent uncontrolled changes by defining a narrow, enforceable boundary. This freezes write scope, not discovery.
When to use
Immediately before editing files or running state-changing commands.
Inputs
- SPEC.md / PLAN.md / TODO.md
- Selected task
- Current repo state
- Git base used to judge the implementation diff
- Optional SPEC implementation diff budget
Workflow
-
Name the exact task.
-
List allowed files/folders as exact paths, directory prefixes, or globs.
-
Do not use repo-wide catch-all patterns (
*,**,**/*) inAllowed writes. If the task genuinely spans multiple areas, enumerate the narrowest relevant prefixes and set a changed-file budget. -
List read-only files/folders.
-
List forbidden paths and operations.
-
Set max files changed and rename/deletion rules when helpful. If SPEC.md has an enforced implementation diff budget, keep the scope's hard file cap at or below that accepted file budget unless scope is renegotiated before implementation.
-
List allowed commands.
-
List compatibility seams and test-integrity triggers before editing.
-
Define clear stop condition.
-
Note that reads/searches are allowed unless explicitly forbidden.
-
Persist the canonical block as
SCOPE.mdbefore the first implementation write when the route invokesscope-freezeandscripts/scope_gate.pyis available. -
After the implementation diff is complete, run:
python scripts/scope_gate.py --base <frozen-base> -
Treat scope-gate
FAILas a hard stop: revert the violating write or renegotiate scope before continuing. TreatREVIEW_REQUIREDas unresolved review, not implicit permission.
Do not widen SCOPE.md after an out-of-scope change merely to make the gate pass. A legitimate scope expansion must be surfaced and agreed before the newly allowed write.
The scope gate's Max files changed is a hard write-boundary rule and remains a FAIL when exceeded. An optional SPEC implementation diff budget is different: verify_gate.py treats file/added-line overruns as REVIEW_REQUIRED so a legitimate but unexpectedly large patch can be reconsidered rather than mislabeled as a functional failure.
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.
- 17d ago Changed · +3 lines 5496ec55cb0f
- 1mo ago Changed · +3 lines a6149ac165da
- 1mo ago First seen · 107 lines · 16 tokens per session scan A 4c28f187e1c8
scope-freeze is a skill published in the GitHub repository tmusser/ai-engineering-skills (6 stars, last pushed 5d ago), licensed MIT. It adds 16 tokens to every session and 985 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 skills, from other repositories
awsl
Run Claude Code JavaScript Workflows through the awsl compatibility runtime. Use when an agent's current task or loaded Skill requires dispatching a Claude Code Workflow but the host cannot execute that Workflow natively, or when awsl workflow inspection, durable run state, resume, or provider diagnostics are needed.
dwi-all-in-one
Apply the relevant Dwi lenses together when several observed workflow problems co-occur. Select only the lenses the task needs, preserve a silent fast path for clear reversible work, and keep authority and evidence explicit. Prefer a focused module when one issue dominates.
dwi-arc
Structure genuinely multi-agent coding work into bounded cells with one writer per scope, explicit integration, and independent review. Use when several disjoint workstreams justify coordination. Do not use for small tasks, overlapping writers, speculative agent fleets, or process artifacts without demonstrated value.
dwi-bridge
Coordinate bounded work between native Claude and Codex workflows with explicit authority, scope, and evidence. Use for read-only consultation or explicitly authorized execution delegation. Do not create a new connector, share secrets, treat messages as authorization, or allow recursive delegation.
dwi-budget
Set and report practical token, context, time, tool-call, and coordination boundaries for coding-agent work. Use when resource use is unclear or needs a checkpoint. Do not invent measurements, monetary savings, cache benefit, or precision that the harness does not expose.
dwi-evidence
Label coding-agent claims by evidence status, preserve provenance and failures, and separate static, runtime, and human proof. Use before completion, comparison, promotion, or handoff. Do not upgrade observations into guarantees or fabricate missing measurements and approvals.