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.
npx skills add AlexZio00/sovereign-skills --skill freezegit clone --depth 1 https://github.com/AlexZio00/sovereign-skillsWrote 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/alexzio00/sovereign-skills/freeze)<a href="https://agentmods.dev/skills/alexzio00/sovereign-skills/freeze"><img src="https://agentmods.dev/badge/skills/alexzio00/sovereign-skills/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/alexzio00/sovereign-skills/freeze"><img src="https://agentmods.dev/badge/skills/alexzio00/sovereign-skills/freeze.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 237 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- low Excessive Agency · line 111 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
- low Excessive Agency · line 185 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00030 | $0.01900 |
| Opus 5 | $0.00015 | $0.00950 |
| Sonnet 5 | $0.00006 | $0.00380 |
| Haiku 4.5 | $0.00003 | $0.00190 |
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 5d 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/freeze — Scope Lock
Declare editable zone — everything outside is frozen.
Dominant Variable
In this task, is the editable scope explicitly declared? — If unclear, scope creep naturally develops during implementation. First of three principles (freeze / careful / guard): freeze = boundary lock (this skill), careful = 3-strike debugging gate, guard = risky path protection.
Trigger
/freeze- "freeze this"
- "scope lock"
- "스코프 잠금"
- "이것만 건드려"
- "나머지 건드리지 마"
- "범위 잠가"
Discard If
- Exploration / research only (no modifications expected)
- Already a clear single-file edit (1 file, ≤10 lines)
- Brainstorming phase (scope not yet finalized before design approval)
Key Assumptions
- User specifies ≥1 modification target — If broken: ask once for clarity; if still unclear, freeze broadly.
- Implementation work follows in the same session — If only declaring scope and ending, this skill is unnecessary.
Architecture
User input (file / module / concept scope)
↓
[PARSE] → classify as editable / frozen / read-only
↓
[DECLARE] → generate FROZEN SCOPE block
↓
[OUTPUT] → emit immediately, then exit
Stage 1: PARSE
Extract from user input:
- editable: explicitly named files / modules / paths — modifications allowed
- frozen: everything else (default frozen if not mentioned)
- read-only: mentioned but modification status unclear → conservatively treat as read-only
If scope is too vague ("everything", "roughly") → ask for clarity once only. Still unclear → freeze more broadly (Invariant 2).
Stage 2: DECLARE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🔒 FROZEN SCOPE — [One-line task description]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✅ EDITABLE (modifications allowed)
[list of files / modules]
❌ FROZEN (no modifications)
[everything else — or "all except above"]
⚠️ READ-ONLY (reference only)
[mentioned but no modifications allowed]
Rules:
- FROZEN files: Edit/Write forbidden. Read only.
- If modification necessity discovered → stop immediately, report to user
- Thaw: user must explicitly say "unfreeze [file]" or "expand scope"
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago Changed 1d285004f809
- 12d ago First seen · 240 lines · 30 tokens per session scan A 56f3099fb280
freeze is a skill published in the GitHub repository AlexZio00/sovereign-skills (129 stars, last pushed 5d ago), licensed MIT. It adds 30 tokens to every session and 1,900 once invoked, about $0.0002 per session on Opus 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-30.
Other skills, from other repositories
nobrainer-review
Use when the owner says nb-review, deep-audit, deep-code-review, or deep-autoreview; explicitly requests an evidence-gated CLOSEOUT, adversarial BUGHUNT or RELEASEGATE; or needs final findings filtered to verified actionable defects. Use nobrainer-build for ordinary implementation and correction work.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.
ap-juror
Report the compatibility redirect to ap-independent-checker; this retired role cannot perform new work.
ijfw-cross-audit
Generate a cross-platform multi-model audit (Trident) on a diff, brief, or artifact. Trigger: 'cross audit', 'Trident', 'second opinion', 'check with other models', 'check with other AIs', 'cross-check this', 'get another perspective', /cross-audit.
doubt-driven-development
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production, security-sensitive logic, irreversible operations), or any time a confident output would be cheaper to verify now…