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/releasenpx skills add u9401066/rootcause-mcp --skill releasegit 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/release)<a href="https://agentmods.dev/skills/u9401066/rootcause-mcp/release"><img src="https://agentmods.dev/badge/skills/u9401066/rootcause-mcp/release.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 | $0.00000 | $0.01728 |
| Opus 5 | $0.00000 | $0.00864 |
| Sonnet 5 | $0.00000 | $0.00346 |
| Haiku 4.5 | $0.00000 | $0.00173 |
Grade A, and why
release 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 3d 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 release — 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: release description: Version release preparation workflow including changelog, version bump, and deployment checks. Triggers: REL, release, 發布, 版本發布, deploy, 部署, publish, 上線, ship, tag, 打標籤, 版本, version bump, 升版. version: 1.0.0 category: workflow compatibility:
- claude-code
- github-copilot
- vscode
- codex-cli orchestrates:
- changelog-updater
- readme-updater
- roadmap-updater
- test-generator
- security-reviewer
- memory-updater allowed-tools:
- read_file
- write_file
- replace_string_in_file
- grep_search
- run_in_terminal
- get_changed_files
版本發布工作流
描述
完整的版本發布準備流程，包含版本號更新、CHANGELOG 生成、文檔同步和部署檢查。
觸發條件
- 「準備發布」「release」「發布版本」
- 「REL: v1.2.0」
📦 發布流程
┌─────────────────────────────────────────────────────────────┐
│ Release Workflow │
├─────────────────────────────────────────────────────────────┤
│ Phase 1: 🔍 發布檢查 (Pre-release Check) │
│ ├─ 確認所有測試通過 │
│ ├─ 執行安全掃描 │
│ ├─ 檢查待處理問題 │
│ └─ 確認 main/master 分支狀態 │
├─────────────────────────────────────────────────────────────┤
│ Phase 2: 🔢 版本決定 (Version Decision) │
│ ├─ 分析變更類型 (MAJOR/MINOR/PATCH) │
│ ├─ 確認版本號 │
│ └─ 更新版本檔案 │
├─────────────────────────────────────────────────────────────┤
│ Phase 3: 📝 文檔更新 (Documentation) │
│ ├─ [changelog-updater] 更新 CHANGELOG │
│ ├─ [readme-updater] 更新 README │
│ ├─ [roadmap-updater] 標記完成項目 │
│ └─ 更新 API 文檔（如有） │
├─────────────────────────────────────────────────────────────┤
│ Phase 4: 🏷️ 標籤準備 (Tagging) │
│ ├─ 建立 Git tag │
│ ├─ 準備 release notes │
│ └─ 確認變更摘要 │
├─────────────────────────────────────────────────────────────┤
│ Phase 5: 🚀 發布 (Publish) │
│ ├─ 推送 tag │
│ ├─ 建立 GitHub Release │
│ └─ 觸發 CI/CD pipeline │
├─────────────────────────────────────────────────────────────┤
│ Phase 6: 📢 發布後 (Post-release) │
│ ├─ 更新 Memory Bank │
│ ├─ 通知相關人員 │
│ └─ 準備下一版本 │
└─────────────────────────────────────────────────────────────┘
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.
- 3d ago First seen · 219 lines · 0 tokens per session scan A aa9ed41b4f22
release is a skill published in the GitHub repository u9401066/rootcause-mcp (0 stars, last pushed 15d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,728 tokens. A static security scan graded it A with 0 findings. It is 100% identical to release, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
release-readiness
Use when preparing to tag, publish, or deploy a genefoundry-router build.
release-readiness
Use when preparing to tag, publish, or promote a hpo-link build.
make-release
Prepare and publish a new release for the wiswa-mcp project.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
release
Version release preparation workflow including changelog, version bump, and deployment checks. Triggers: REL, release, 發布, 版本發布, deploy, 部署, publish, 上線, ship, tag, 打標籤, 版本, version bump, 升版.
changelog-updater
Auto-update CHANGELOG.md following Keep a Changelog format. Triggers: CL, changelog, 變更, 版本, version, 更新日誌, whatsnew, release notes, 發布說明, 變更紀錄, history, 歷史, 更新紀錄, 新功能, new features, breaking changes.