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/elvezjp/ixv-agents/dev-notify-smnpx skills add elvezjp/ixv-agents --skill dev-notify-smgit 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/dev-notify-sm)<a href="https://agentmods.dev/skills/elvezjp/ixv-agents/dev-notify-sm"><img src="https://agentmods.dev/badge/skills/elvezjp/ixv-agents/dev-notify-sm.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.00074 | $0.01754 |
| Opus 5 | $0.00037 | $0.00877 |
| Sonnet 5 | $0.00015 | $0.00351 |
| Haiku 4.5 | $0.00007 | $0.00175 |
Grade A, and why
dev-notify-sm 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 6d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Notify SM
報告ファイル（queue/reports/{task_id}.yaml）を書き込んだ後、SMに send-keys で完了通知を送る。通信ロスト対策として idle 確認とリトライロジックを含む。
When to Use
dev-write-reportでqueue/reports/{task_id}.yamlを書き込んだ直後- タスク完了後の通知は義務（省略禁止）
Prerequisites
queue/reports/{task_id}.yamlが既に書き込まれていること- 報告ファイルが存在しない状態で通知を送らないこと
Instructions
Step 1: SMの状態確認
tmux capture-pane -t ixv-agents:0.1 -p | tail -5
Step 2: idle / busy 判定
| 表示 | 状態 | Action |
|---|---|---|
❯ （末尾） |
idle | → Step 4 へ |
bypass permissions on |
idle | → Step 4 へ |
thinking |
busy | → Step 3 へ |
Esc to interrupt |
busy | → Step 3 へ |
Effecting… |
busy | → Step 3 へ |
Boondoggling… |
busy | → Step 3 へ |
Puzzling… |
busy | → Step 3 へ |
Calculating… |
busy | → Step 3 へ |
Fermenting… |
busy | → Step 3 へ |
Crunching… |
busy | → Step 3 へ |
Step 3: busy の場合 — リトライ（最大3回）
sleep 10
10秒待機して Step 1 に戻る。
- リトライ上限: 最大3回
- 3回リトライ後も busy の場合: Step 4 へ進む
- 報告ファイルは既に書かれているため、SMが
sm-scan-reportsで発見できる
- 報告ファイルは既に書かれているため、SMが
Step 4: send-keys 送信（2回に分ける）
【1回目】 メッセージを送る：
tmux send-keys -t ixv-agents:0.1 'Dev{N}、タスク完了しました。報告書を確認してください。'
【2回目】 Enterを送る：
tmux send-keys -t ixv-agents:0.1 Enter
重要: 必ず 2回の別々のBash呼び出し で実行する。1回にまとめてはいけない。
Step 5: 停止
通知送信後、処理を終了する。次のタスクはSMから send-keys で起こされるまで待つ。
「報告を送信しました。ここで停止します。」
Examples
Example 1: SM が idle の場合（即時送信）
Step 1: SM の状態確認
tmux capture-pane -t ixv-agents:0.1 -p | tail -5
出力:
tasks/dev1.yaml を確認します。
...
❯
Step 2: ❯ が表示 → idle → Step 4 へ
Step 4: send-keys 送信
tmux send-keys -t ixv-agents:0.1 'Dev1、タスク完了しました。報告書を確認してください。'
tmux send-keys -t ixv-agents:0.1 Enter
Example 2: SM が busy → リトライ後に送信
Step 1（1回目）: SM の状態確認
Esc to interrupt
→ busy → Step 3 へ
Step 3（1回目）: 10秒待機
sleep 10
Step 1（2回目）: SM の状態確認
❯
→ idle → Step 4 へ
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.
- 6d ago First seen · 177 lines · 74 tokens per session scan A ec6f4ee47465
dev-notify-sm is a skill published in the GitHub repository elvezjp/ixv-agents (5 stars, last pushed 28d ago), licensed MIT. It adds 74 tokens to every session and 1,754 once invoked, about $0.0004 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…
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…