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 Stanshy/AgentHub --skill spec-updategit clone --depth 1 https://github.com/Stanshy/AgentHubWrote 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/stanshy/agenthub/spec-update)<a href="https://agentmods.dev/skills/stanshy/agenthub/spec-update"><img src="https://agentmods.dev/badge/skills/stanshy/agenthub/spec-update/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/stanshy/agenthub/spec-update"><img src="https://agentmods.dev/badge/skills/stanshy/agenthub/spec-update.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.00031 | $0.00870 |
| Opus 5.5 | $0.00012 | $0.00348 |
| Sonnet 5.5 | $0.00006 | $0.00174 |
| Haiku 4.5 | $0.00003 | $0.00087 |
Grade A, and why
spec-update 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 1mo 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
規範文件更新
修改任何 .knowledge/specs/ 下的規範文件時，必須透過此 skill 執行，確保版本號遞增、變更有記錄、相關任務被通知。
使用方式
/spec-update <spec-file> <變更摘要>
參數
$0: 規範文件路徑（如.knowledge/specs/api-design.md）$ARGUMENTS: 完整參數（含變更摘要）
執行步驟
STEP 1 — 讀取目標規範文件
讀取 $0，確認：
- 當前版本號（文件標題或頂部 metadata 中的
vX.Y） - 文件結構與現有內容
⛔ STEP 2 — 確認變更範圍
說明本次變更：
- 變更內容：新增 / 修改 / 刪除了什麼
- 影響範圍：哪些模組、API、功能受影響
- 向後相容性：是否有 breaking change
輸出：
📋 變更摘要
規範文件：$0
當前版本：vX.Y
變更類型：[新增欄位 / 修改行為 / 刪除功能 / 其他]
影響範圍：[描述]
Breaking change：[是 / 否]
✋ 確認變更範圍正確後再繼續。
STEP 3 — 執行變更
對 $0 進行實際修改。
⛔ STEP 4 — 遞增版本號
在規範文件頂部更新版本號：
- Minor change（新增、修改）：
vX.Y→vX.Y+1 - Breaking change：
vX.Y→vX+1.0
在文件頂部加入變更記錄（若無 Changelog 區塊則新增）：
## Changelog
### vX.Y+1 — {YYYY-MM-DD}
{變更摘要}
✋ 確認版本號已遞增、變更記錄已寫入後再繼續。
STEP 5 — 更新 file-index.md
找到 .knowledge/file-index.md，更新對應規範文件的版本標註：
| `.knowledge/specs/api-design.md` | API 設計規格 vX.Y+1（🔴 規範） |
STEP 6 — 掃描受影響任務
!find .tasks -name "*.md" 2>/dev/null | xargs grep -l "api-design\|data-model\|feature-spec" 2>/dev/null | head -10
列出目前 in_progress 或 assigned 狀態、且與本規範相關的任務。
STEP 7 — 輸出通知
✅ 規範更新完成
規範文件：$0
版本：vX.Y → vX.Y+1
file-index 已更新：✅
受影響的進行中任務：
- T3: {名稱} (in_progress → 需確認是否受影響)
- T5: {名稱} (assigned → 執行前請重新閱讀規範)
建議動作：
1. 通知相關 L2 Agent 重新讀取規範後繼續執行
2. 若有 breaking change，請 L1 確認已完成任務是否需要返工
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.
- 1mo ago First seen · 103 lines · 31 tokens per session scan A 465e94d9c06a
spec-update is a skill published in the GitHub repository Stanshy/AgentHub (204 stars, last pushed 6mo ago), licensed MIT. It adds 31 tokens to every session and 870 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
project-setup-info-local
Comprehensive setup steps to help the user create complete project structures in a VS Code workspace; this tool is designed for full project initialization and scaffolding, not for creating individual files. When to use this tool: user wants to create a new complete project from scratch; setting up entire project…
md-hive-sync
Munder Difflin hive sync — runs the start-of-task hive protocol steps: reads memory.md, checks inbox/ for new messages, and reminds you to record durable facts in memory.md and write coordination files before ending. Use when asked to "sync with the hive", "check my inbox", "hive status", or "hive sync". Proactively…
comet-native
A workflow for managing Native changes in Comet, where requirements, progress, and acceptance results are saved in project files. It uses the Comet command-line runtime to move through defined work stages.
comet-github-idea-to-issue
A workflow for turning a local idea, bug observation, or improvement proposal into a focused GitHub Issue draft. GitHub Issues are shared records for bugs, features, questions, and maintenance work.
generate-rfcs
Break the PRD into sequenced implementation RFCs under RFCs/ with an RFCS.md index, then cold-read each RFC for gaps.
create-request
Create, update, or scan per-task request tickets for progress tracking. These are date-prefixed non-lifecycle docs under requests/, NOT feature-level requirements (use /req-analyze for those). Use when: tracking task progress, updating completion status, scanning incomplete requests, checking request status dashboard.…