guard

guard is a skill for Claude Code from tranhieutt/software_development_department. It costs 32 tokens per session (526 once invoked), scanned A, original, MIT.

A safety check that reads a project's freeze status before work on the main branch. A code freeze is a period when non-critical changes are temporarily blocked.

In plain words
What is it for?
Use it to check whether development or merging is allowed, review the freeze reason, and classify work as an emergency fix, release task, or non-critical change.
Why use it?
It prevents ordinary feature work or refactoring from being merged during a freeze, while allowing urgent fixes and release preparation.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: agent in frontmatter.

Good fit Use it to check whether development or merging is allowed, review the freeze reason, and classify work as an emergency fix, release task, or non-critical change.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tranhieutt/software_development_department/guard
Install

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.

Any agent
npx skills add tranhieutt/software_development_department --skill guard
Clone the repo
git clone --depth 1 https://github.com/tranhieutt/software_development_department

Made for: Claude Code.

Wrote 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.

agentmods badge for guard

README.md
[![agentmods](https://agentmods.dev/badge/skills/tranhieutt/software_development_department/guard/github.svg)](https://agentmods.dev/skills/tranhieutt/software_development_department/guard)
Your own site
<a href="https://agentmods.dev/skills/tranhieutt/software_development_department/guard"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/guard/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.

agentmods 80×15 button for guard

Your own site · 80×15
<a href="https://agentmods.dev/skills/tranhieutt/software_development_department/guard"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/guard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 526 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.00526
Opus 5 $0.00016 $0.00263
Sonnet 5 $0.00006 $0.00105
Haiku 4.5 $0.00003 $0.00053

Measured 7d ago against content hash 5c348c5b0aaa, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

guard 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 7d 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.

.claude/skills/guard/SKILL.md · 78 lines

What it actually says

Guard Check

Check the freeze status of the codebase. Use as a gate check before any operations on the main branch.

Workflow

1. Read .freeze

If it does not exist:

✅ CLEAR — No active freeze.
Development and merging can proceed normally.

Stop here.

If it exists, proceed to step 2.

2. Display Freeze Warning

🔒 CODEBASE IS FROZEN

Reason  : [REASON from .freeze]
Since   : [FROZEN_AT]
Branch  : [BRANCH]
Duration: [calculated from FROZEN_AT to current time]

⚠️  Non-critical merges are blocked during a freeze period.

3. Categorize the Request

Ask:

"What type of operation is this?"

A) Urgent Hotfix — production bug, security patch B) Release Artifact — changelog, version bump, release notes C) Non-critical — feature, refactor, chore, normal docs

If A or B: Allow to proceed with a note:

"⚠️ Permitted to proceed. Note that this is a freeze period — execute only necessary operations."

If C: Block and instruct:

"🚫 Non-critical changes must wait until after /unfreeze. Save your work and continue after the release is complete."

4. Suggestions

  • /unfreeze — If the release is finished
  • /release-checklist — If currently in the release process
  • /hotfix — If an urgent fix deployment is needed

Edge Cases

  • No .freeze: Just report CLEAR, ask no further questions.
  • User unsure of operation type: Ask for more details to categorize correctly before deciding.
  • /freeze — Lock codebase
  • /unfreeze — Remove freeze
  • /hotfix — Urgent deployment during freeze
  • /release-checklist — Full release workflow
Changes

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.

  1. 7d ago First seen · 78 lines · 32 tokens per session scan A 5c348c5b0aaa

Subscribe to this mod's changes

guard is a skill published in the GitHub repository tranhieutt/software_development_department (72 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 526 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.

Related

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.

tuliosousapro/SaaS-blueprint · 39 tokens

conventional-commits

Enforces Conventional Commits format for git commit messages. Use when formatting commits or validating message structures. For git commands, see git-control.

tuliosousapro/SaaS-blueprint · 34 tokens

git-control

Standardizes git operations, branch management, and disaster recovery. Use when committing, branching, or resolving conflicts. For commit formatting, see conventional-commits.

tuliosousapro/SaaS-blueprint · 35 tokens

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.

easyinplay/harnessed · 62 tokens

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.

tuliosousapro/SaaS-blueprint · 63 tokens

storozh

Advisory semantic guard over a changeset manifest before it lands in shared state. Use after a multi-repo session produces a changeset-manifest (mirabilis C1) and before the co-sign push gate — classify each unit's routing against the darwin routing-policy (C3) and NLI-check each unit against the shield corpus (claims…

AlexShchuka/neuro-matrix · 104 tokens