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 agentmods add skills/u9401066/rootcause-mcp/skill-generatornpx skills add u9401066/rootcause-mcp --skill skill-generatorgit clone --depth 1 https://github.com/u9401066/rootcause-mcpWrote 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/rootcause-mcp/skill-generator)<a href="https://agentmods.dev/skills/u9401066/rootcause-mcp/skill-generator"><img src="https://agentmods.dev/badge/skills/u9401066/rootcause-mcp/skill-generator.svg" alt="Measured on agentmods" 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.00000 | $0.01111 |
| Opus 5 | $0.00000 | $0.00556 |
| Sonnet 5 | $0.00000 | $0.00222 |
| Haiku 4.5 | $0.00000 | $0.00111 |
Grade A, and why
skill-generator 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.
This is a copy
100% identical to skill-generator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill 生成器
描述
自動生成符合標準的 SKILL.md 和資料夾結構。
觸發條件
- 「新增 skill」「建立技能」「create skill」「SG」
標準格式規範
YAML Frontmatter(必要)
---
name: skill-name # kebab-case 必須(小寫 + 連字號)
description: 描述 # 包含 WHAT + WHEN + Triggers
category: core # core/workflow/meta/integration
version: 1.0.0 # SemVer
compatibility: # 支援的平台(可選)
- claude-code
- github-copilot
- vscode
allowed-tools: # 可使用的工具(可選)
- read_file
- write_file
orchestrates: # 組合的其他 skills(workflow 用)
- skill-a
- skill-b
---
命名規則
| 規則 | 正確 ✅ | 錯誤 ❌ |
|---|---|---|
| kebab-case | code-reviewer |
codeReviewer, CodeReviewer |
| 小寫 | git-precommit |
Git-Precommit |
| 有意義 | test-generator |
tg, testgen |
| 無底線 | memory-bank |
memory_bank |
資料夾結構
.claude/skills/
└── skill-name/
├── SKILL.md # 主要技能定義(必要)
├── references/ # 詳細參考文檔(可選)
│ ├── examples.md
│ └── api.md
├── templates/ # 範本檔案(可選)
│ └── template.py
└── scripts/ # 輔助腳本(可選)
└── helper.ps1
生成流程
Step 1: 收集資訊
❓ Skill 名稱:[輸入名稱,會自動轉 kebab-case]
❓ 描述:[一句話描述 + 觸發詞]
❓ 類別:[core/workflow/meta/integration]
❓ 需要額外資料夾嗎?[references/templates/scripts]
Step 2: 驗證
- ✅ 名稱是 kebab-case
- ✅ 名稱不重複
- ✅ 描述包含觸發詞
- ✅ 類別有效
Step 3: 生成
📁 建立 .claude/skills/{name}/
📄 建立 .claude/skills/{name}/SKILL.md
📁 建立子資料夾(如需要)
📝 更新 AGENTS.md skills 清單
使用範例
「新增 skill: api-tester」
「SG 建立 docker 管理技能」
「create skill for database migrations」
輸出範本
當你說「新增 skill: example-skill」,我會生成:
---
name: example-skill
description: [描述]. Triggers: [觸發詞列表].
category: core
version: 1.0.0
compatibility:
- claude-code
- github-copilot
- vscode
---
# [Skill 名稱]
## 描述
[詳細描述]
## 觸發條件
- 「[觸發詞 1]」「[觸發詞 2]」
## 執行流程
[流程圖或步驟]
## 參數
| 參數 | 說明 | 預設 |
|------|------|------|
| `--option` | 說明 | false |
## 使用範例
[範例 1] [範例 2]
## 輸出格式
[預期輸出格式]
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 First seen · 170 lines · 0 tokens per session scan A af5bce4a298b
skill-generator is a skill published in the GitHub repository u9401066/rootcause-mcp (0 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,111 tokens. A static security scan graded it A with 0 findings. It is 100% identical to skill-generator, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
skill-generator
Generate new skills with standardized structure and frontmatter. Triggers: SG, new skill, 新增 skill, 建立技能, create skill, 新技能, 產生技能, generate skill, 技能模板, skill template, add skill, 加技能, make skill.
detecting-pv-signals
Computes disproportionality signals — PRR, ROR, EBGM, and IC (BCPNN) — over FAERS / OpenFDA drug-event data to flag potential safety signals. Use when the user wants to mine spontaneous-report data for drug-reaction associations, build a 2x2 contingency table, compute a Proportional Reporting Ratio or Reporting Odds…
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…
structuring-radiology-reports
Converts free-text radiology narratives into structured findings and impression — with measurements, laterality, anatomy, and follow-up recommendations — after OpenMed NER. Use when the user has a CT/MRI/X-ray/ultrasound/mammography report and needs the sections split (technique, comparison, findings, impression)…
deidentifying-clinical-text
Remove, mask, or replace PHI/PII in clinical free text on-device with OpenMed's deidentify(). Use when the user needs to de-identify medical notes, strip patient identifiers, redact PHI before sharing or analysis, anonymize discharge summaries, or pick a de-id method (mask vs remove vs replace vs hash vs shiftdates).…
evaluating-with-leakage-gates
Evaluate an OpenMed de-identification or clinical NER model against the leakage-first release gates G1a through G8, which gate releases on residual PHI leakage rather than on F1. Use when the user wants to run the OpenMed eval harness on a synthetic golden set, decide whether a de-id model is RELEASABLE or…