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 u9401066/template-is-all-you-need --skill skill-health-checkgit clone --depth 1 https://github.com/u9401066/template-is-all-you-needWrote 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/u9401066/template-is-all-you-need/skill-health-check)<a href="https://agentmods.dev/skills/u9401066/template-is-all-you-need/skill-health-check"><img src="https://agentmods.dev/badge/skills/u9401066/template-is-all-you-need/skill-health-check/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/u9401066/template-is-all-you-need/skill-health-check"><img src="https://agentmods.dev/badge/skills/u9401066/template-is-all-you-need/skill-health-check.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.00077 | $0.01653 |
| Opus 5 | $0.00039 | $0.00826 |
| Sonnet 5 | $0.00015 | $0.00331 |
| Haiku 4.5 | $0.00008 | $0.00165 |
Grade A, and why
skill-health-check 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 12d 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill & Instruction 健康檢查
描述
全面檢查專案中所有 Skills、Copilot Instructions、Chatmodes 和 Bylaws 的健康度、一致性和新鮮度。 這是一個自省型 Skill，讓 Copilot 能檢查自己的設定是否需要翻新。
觸發條件
- 「檢查 skill 健康度」「SHC」「skill health check」
- 「翻新 skill」「檢查過期」「audit skills」
- 「instruction check」「技能檢查」
🔧 操作步驟
Step 1: 掃描 Skill 目錄結構
list_dir(".claude/skills/")
對每個 skill 子目錄：
- 檢查
SKILL.md存在 - 讀取 frontmatter 驗證必要欄位
- 記錄版本號與最後修改時間
必要 frontmatter 欄位：
name— skill 識別名稱description— 包含觸發詞的描述version— 語義化版本category— 類別分類compatibility— 支援的平台列表allowed-tools或dependencies— 工具/依賴宣告
Step 2: 檢查 copilot-instructions.md 同步性
read_file(".github/copilot-instructions.md")
比對：
- Instructions 中的 Skill 表格 vs 實際
.claude/skills/目錄 - 觸發詞是否一致
- 是否有 instructions 中提到但不存在的 skill
- 是否有存在但未在 instructions 中登記的 skill
Step 3: 驗證 Chatmode 健康
list_dir(".github/") # 找 *.chatmode.md
檢查：
- frontmatter 格式正確
tools列表使用有效名稱- description 是否有意義
- 是否有重複功能的 chatmode
Step 4: Bylaws 一致性
list_dir(".github/bylaws/")
- bylaws 提及的 skill 名稱是否與實際一致
- CONSTITUTION.md 的原則是否被 skill 遵守
Step 5: 依賴圖分析
解析所有 skill 的 dependencies 和 orchestrates 欄位：
- 繪製依賴關係
- 找出斷裂的依賴（宣告了但不存在的）
- 找出循環依賴
- 找出孤立的 skill（沒有被任何 workflow 引用）
Step 6: 新鮮度評估
| 條件 | 狀態 |
|---|---|
| 90 天內更新 | 🟢 新鮮 |
| 90-180 天 | 🟡 建議檢查 |
| > 180 天 | 🔴 需要翻新 |
Step 7: 自動修復建議
根據發現的問題，提供可選的自動修復：
- 更新 copilot-instructions.md 的 skill 表格
- 補齊缺少的 frontmatter 欄位
- 建議過期 skill 的更新方向
📊 輸出格式
# 🏥 Skill & Instruction 健康報告
📅 檢查日期：YYYY-MM-DD
📁 Skills 位置：.claude/skills/
---
## 📊 總覽
| 指標 | 值 |
|------|-----|
| Skills 總數 | XX |
| 結構完整 | XX/XX ✅ |
| 版本新鮮 | XX 新鮮 / XX 過期 |
| 指令同步 | ✅ 同步 / ⚠️ 不同步 |
| 依賴完整 | ✅ 完整 / ❌ 斷裂 |
---
## 🗂️ Skill 清單
| Skill | 版本 | 類別 | 新鮮度 | 狀態 |
|-------|------|------|--------|------|
| git-precommit | v2.2.0 | workflow | 🟢 | ✅ |
| code-reviewer | v2.2.0 | quality | 🟢 | ✅ |
| ... | | | | |
---
## ✅ 健康項目
1. ...
## ⚠️ 需要關注
1. ...
## ❌ 需要修復
1. ...
---
## 🔗 依賴圖
git-precommit (workflow) ├── memory-updater ├── readme-updater ├── changelog-updater ├── roadmap-updater └── ddd-architect
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.
- 12d ago First seen · 225 lines · 0 tokens per session scan A 359c25da2dc9
skill-health-check is a skill published in the GitHub repository u9401066/template-is-all-you-need (3 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 77 tokens to every session and 1,653 once invoked, about $0.0004 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-31.
Other skills, from other repositories
clean-architecture-dotnet
Use when domain logic leaks into API/Infrastructure, project references violate layer boundaries, or you need to decide between CQS (always), CQRS bus (complex domains), and DDD patterns (invariants and events).
mutation-testing
Use when running mutation testing, killing mutants, verifying test quality, checking mutation score, or analyzing survivors after the test baseline is green.
generate-microcks-openapi-samples
Use when creating OpenAPI mock examples for Microcks, setting up request/response routing with dispatchers, or mapping request fields to mock responses.
outside-in-tdd
Use when writing tests from the outside-in, defining behavior before code, or any feature where tests should start from observable business behavior and let internal design emerge.
extracting-code-structure
Use when listing all methods, functions, or classes in a file, exploring unfamiliar code, getting API overviews, or deciding what to read selectively without loading entire files.
querying-yaml
Use when querying YAML files, filtering or transforming configuration data, or extracting specific fields from large YAML files like docker-compose.yml or GitHub Actions workflows without loading entire files (saves 80-95% context).