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 tranhieutt/software_development_department --skill freezegit clone --depth 1 https://github.com/tranhieutt/software_development_departmentWrote 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/tranhieutt/software_development_department/freeze)<a href="https://agentmods.dev/skills/tranhieutt/software_development_department/freeze"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/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/tranhieutt/software_development_department/freeze"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/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.00038 | $0.00487 |
| Opus 5 | $0.00019 | $0.00244 |
| Sonnet 5 | $0.00008 | $0.00097 |
| Haiku 4.5 | $0.00004 | $0.00049 |
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 8d 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.
What it actually says
Code Freeze
Lock the codebase in preparation for a release. Create a .freeze file containing freeze information.
Workflow
1. Read Current Status
Check if .freeze already exists by reading the file. If it exists, display the information and ask:
"The codebase is currently frozen for: [REASON]. Do you want to override the current freeze? (yes/no)"
If no, stop.
2. Get Freeze Reason
If no argument is provided, ask:
"What is the reason for the freeze? (e.g., 'Release v2.1.0', 'Hotfix deployment', 'Sprint end')"
3. Create .freeze File
Write the following content:
FROZEN=true
REASON=[reason]
FROZEN_AT=[ISO timestamp]
BRANCH=[current branch from git rev-parse --abbrev-ref HEAD]
4. Notification
Display:
🔒 CODEBASE FROZEN
Reason : [reason]
Time : [timestamp]
Branch : [branch]
Non-critical merges are blocked. Only hotfixes are permitted.
To unlock: /unfreeze
5. Suggested Next Steps
/release-checklist— Run the full release checklist/guard— Check the freeze status at any time/unfreeze— Unlock after the release is complete
Edge Cases
- Existing freeze: Ask for override confirmation before overwriting.
- No git repository: Still create
.freezebut omit the BRANCH field.
Related Skills
/guard— Check freeze status before merge/deploy/unfreeze— Remove freeze after release/release-checklist— Full release workflow/hotfix— Deploy urgent fixes during a freeze
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.
- 8d ago First seen · 73 lines · 38 tokens per session scan A 0d3020e058ad
freeze is a skill published in the GitHub repository tranhieutt/software_development_department (72 stars, last pushed 4mo ago), licensed MIT. It adds 38 tokens to every session and 487 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-09-03.
Other skills, from other repositories
changelog
Generates and maintains changelogs following Keep a Changelog format. Use when updating release notes, finishing tasks, or tagging versions. For version bumps, see semantic-versioning.
ship-preflight
Stage ⑤.a Ship sub — release-preflight gate. Runs harnessed release-preflight (read-only: CHANGELOG [Unreleased] non-empty + version + git-clean + tag-absent). A failing gate blocks shipping. Nothing is pushed/published/tagged here.
semantic-versioning
Manages project versioning following Semantic Versioning (SemVer) principles. Calculates increments based on changes and synchronizes version across documentation and metadata. Use when the user asks to "bump the version", "prepare a release", or when the changelog skill calls for a release.
release-skills
A release workflow for preparing and publishing a new version of a software project. A release is a named version that may include updated version files, release notes, tags, or a GitHub Release.
comet-archive
A workflow for the fifth stage of Comet Classic: archiving a completed change, merging its specification updates, and finishing the branch. It uses Comet commands and a fixed layout for tracking the change.
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.