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 elvezjp/ixv-agents --skill sm-update-specgit clone --depth 1 https://github.com/elvezjp/ixv-agentsWrote 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/elvezjp/ixv-agents/sm-update-spec)<a href="https://agentmods.dev/skills/elvezjp/ixv-agents/sm-update-spec"><img src="https://agentmods.dev/badge/skills/elvezjp/ixv-agents/sm-update-spec/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/elvezjp/ixv-agents/sm-update-spec"><img src="https://agentmods.dev/badge/skills/elvezjp/ixv-agents/sm-update-spec.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.00117 | $0.02553 |
| Opus 5.5 | $0.00047 | $0.01021 |
| Sonnet 5.5 | $0.00023 | $0.00511 |
| Haiku 4.5 | $0.00012 | $0.00255 |
Grade A, and why
sm-update-spec 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 2mo 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SM Update Spec
フェーズコンテキストに応じて、プロジェクトの仕様文書（CONSTITUTION.md / README.md）を更新する。
When to Use
- Phase 1: POから
constitution_updateタスクを受領した時 - Phase 2: POから
spec_updateタスクを受領した時 - Phase 3: 計画に基づく仕様詳細化が必要な時
- Phase 6: POから
backlog_updateタスクを受領した時
Instructions
Step 1: 現在のフェーズを確認
queue/po_to_sm.yaml の task_type から現在のフェーズを確認する。
| task_type | Phase | 更新対象 |
|---|---|---|
| constitution_update | 1 | CONSTITUTION.md |
| spec_update | 2 | README.md |
| plan | 3 | README.md（詳細化） |
| backlog_update | 6 | README.md（Backlog） |
Step 2: フェーズ別の更新対象を特定
Phase 1: CONSTITUTION.md 更新
更新対象セクション: ## 1. 存在意義（Purpose）
更新手順:
CONSTITUTION.mdを読み取り## 1. 存在意義（Purpose）セクションを確認po_to_sm.yamlのsummary/acceptance_criteria/notesに基づき内容を記入- テンプレート文言（「このプロジェクトが存在する理由を明記する」）を具体的な目的に置換
未記入判定パターン（テンプレート文言のまま/空/プレースホルダー）:
- 「このプロジェクトが存在する理由を明記する」
- 「TODO」「TBD」「要記入」
{purpose}/[目的を記入]
Phase 2: README.md 更新（仕様策定）
更新対象セクション:
| セクション | 更新内容 |
|---|---|
## Goal |
目的/達成したい価値の追加・修正 |
## Scope |
含める範囲/Non-Goalsの追加・修正 |
## Requirements |
機能要件の追加 |
## Acceptance Criteria |
受入条件（テスト観点）の追加 |
## Constraints |
技術/運用/セキュリティ制約の追加 |
## Backlog |
新規エントリ追加（Status: ready） |
更新手順:
README.mdを読み取りpo_to_sm.yamlのsummary/acceptance_criteria/constraints/notesを確認- 該当セクションに要件を追加
- Backlog テーブルに新規エントリを追加
Backlog エントリ追加例:
## Backlog
| ID | Priority | Summary | Status |
|----|----------|---------|--------|
| REQ-20260201-001 | P1 | ダークモード対応 | ready |
Phase 3: README.md 更新（仕様詳細化）
更新手順:
docs/の計画書を読み取り- 計画内容に基づき、README.md の Requirements / Acceptance Criteria を具体化
- 必要に応じて Constraints を追加
注意: 計画書（docs/）は補助資料。仕様として有効なのは README.md の記載のみ。 計画書に重要な決定がある場合、README.md の該当セクションへ要点を反映する。
Phase 6: README.md 更新（Backlog ステータス更新）
前提: 本スキルは Phase 6 の ACCEPT 分岐（PO が backlog_update を発行した場合）で起動する。REJECT / REVIEW_NEEDED 分岐では起動しない（SPEC.md §5.6 参照）。
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 234 lines · 117 tokens per session scan A fd8c2bf86589
sm-update-spec is a skill published in the GitHub repository elvezjp/ixv-agents (5 stars, last pushed 2mo ago), licensed MIT. It adds 117 tokens to every session and 2,553 once invoked, about $0.0005 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-31.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.