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 guardgit 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/guard)<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.
<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>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.00032 | $0.00526 |
| Opus 5 | $0.00016 | $0.00263 |
| Sonnet 5 | $0.00006 | $0.00105 |
| Haiku 4.5 | $0.00003 | $0.00053 |
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.
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.
Related Skills
/freeze— Lock codebase/unfreeze— Remove freeze/hotfix— Urgent deployment during freeze/release-checklist— Full release workflow
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.
- 7d ago First seen · 78 lines · 32 tokens per session scan A 5c348c5b0aaa
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.
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.
conventional-commits
Enforces Conventional Commits format for git commit messages. Use when formatting commits or validating message structures. For git commands, see git-control.
git-control
Standardizes git operations, branch management, and disaster recovery. Use when committing, branching, or resolving conflicts. For commit formatting, see conventional-commits.
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.
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…