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 akiojin/skills --skill speckit-updategit clone --depth 1 https://github.com/akiojin/skillsWrote 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/akiojin/skills/speckit-update)<a href="https://agentmods.dev/skills/akiojin/skills/speckit-update"><img src="https://agentmods.dev/badge/skills/akiojin/skills/speckit-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/akiojin/skills/speckit-update"><img src="https://agentmods.dev/badge/skills/akiojin/skills/speckit-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.00103 | $0.00735 |
| Opus 5 | $0.00051 | $0.00367 |
| Sonnet 5 | $0.00021 | $0.00147 |
| Haiku 4.5 | $0.00010 | $0.00073 |
Grade A, and why
speckit-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 9d 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
Spec Kit Update
GitHub Spec Kit: https://github.com/github/spec-kit
Overview
GitHub公式 spec-kit の新リリースを既存リポジトリの .specify/ に反映し、既存の運用ルール（日本語化、ブランチ非操作、SPEC ID形式）を保持したまま更新する。
Workflow
1) 現状把握
- リポジトリ内の spec-kit ベースバージョンを特定する（例:
rg -n "v0\\.0\\.[0-9]+"）。 - spec-kit 由来の対象を列挙する（例:
.specify/,.claude/commands/speckit.*.md）。
2) 上流バージョン確認
- GitHubの spec-kit 最新タグ/リリースを確認する（Web検索またはタグ一覧）。
- 更新対象タグを決め、該当タグを
git cloneで取得する。
3) 差分取得
- 上流タグ間 diff か、上流→ローカル diff を取得する。
- 変更対象を重点確認する:
templates/templates/commands/scripts/（bash/powershell）memory/
- 追加/削除ファイルも必ず把握する。
4) ローカル適用
- 上流の変更をローカルに反映する。
- 必須のローカル制約を再適用:
- すべて日本語
- ブランチ操作の禁止（スクリプト/コマンドに checkout/switch/create が残らない）
- SPEC ID は
SPEC-[UUID8桁]
- 既存の運用差分がある場合は、短い理由を記録する。
5) ドキュメント更新
- バージョン表記を更新する（例:
CLAUDE.md,.specify/README.md）。 - 更新履歴がある場合は追記する。
6) 検証と報告
- 主要スクリプトの動作を軽く確認する（
--help,--json等）。 rgで英語の残存や旧バージョン表記がないか確認する。- 変更点サマリ、影響範囲、未対応の差分を明確に報告する。
Guardrails
- ブランチ作成/切替は行わない（ユーザー管理）。
- SPEC ID 形式は必ず
SPEC-[UUID8桁]を維持する。 - 上流の英語テンプレートは日本語に翻訳してから反映する。
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.
- 9d ago First seen · 61 lines · 103 tokens per session scan A f23706bd1b2d
speckit-update is a skill published in the GitHub repository akiojin/skills (8 stars, last pushed 6mo ago), licensed MIT. It adds 103 tokens to every session and 735 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…