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-scan-reportsgit 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-scan-reports)<a href="https://agentmods.dev/skills/elvezjp/ixv-agents/sm-scan-reports"><img src="https://agentmods.dev/badge/skills/elvezjp/ixv-agents/sm-scan-reports/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-scan-reports"><img src="https://agentmods.dev/badge/skills/elvezjp/ixv-agents/sm-scan-reports.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.00086 | $0.02862 |
| Opus 5 | $0.00043 | $0.01431 |
| Sonnet 5 | $0.00017 | $0.00572 |
| Haiku 4.5 | $0.00009 | $0.00286 |
Grade A, and why
sm-scan-reports 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 10d 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SM Scan Reports
queue/reports/ 配下の全報告ファイルをスキャンし、queue/dashboard.md と照合して未処理の報告を特定する。通信ロスト対策として、起こされるたびに毎回全スキャンを行う。
When to Use
- Devから send-keys で起こされた時（毎回必須）
- Phase 5 で作業進捗を確認する時
- コンパクション復帰後
- 理由に関係なく起こされたら毎回実行
Why Full Scan is Required
- Devが報告ファイルを書いた後、send-keys が届かないことがある
- SMが処理中だと、Enter がパーミッション確認等に消費される
- 報告ファイル自体は正しく書かれているので、スキャンすれば発見できる
- これにより「send-keys が届かなくても報告が漏れない」安全策となる
Instructions
Step 1: 全報告ファイルを一覧取得
ls -la queue/reports/
TEMPLATE.yaml を除く全ファイルが対象。
Step 2: 各報告ファイルを読み取り
各報告ファイルを読み取り、以下のフィールドを確認する：
| フィールド | 確認内容 |
|---|---|
| task_id | タスク識別子 |
| status | done / blocked / needs_review |
| summary | 結果概要 |
| changes | 変更点 |
| artifacts | 成果物ファイルパス |
| issues | 問題点・ブロッカー |
Report Schema（SPEC.md 2.3.4準拠）:
schema_version: "1.0"
created_at: "YYYY-MM-DDTHH:MM:SSZ"
updated_at: "YYYY-MM-DDTHH:MM:SSZ"
task_id: "TASK-YYYYMMDD-###"
status: "done"
summary: "200文字以内の結果概要"
changes:
- "変更点の箇条書き"
artifacts:
- "ファイルパス"
issues:
- "課題や不具合"
Step 3: dashboard.md と照合
queue/dashboard.md の以下のセクションと照合する：
- Backlog Status: タスクの進捗状況
- Agent Status: 各Devの作業状況
- Blockers: ブロッカー一覧
Step 3.5: Definition of Done 突合検証（status: done レポートのみ）
SPEC.md §2.4.3 に基づく必須検証。status: done の報告について、対応タスクの definition_of_done を読み込み、レポートの changes / artifacts と突合する。
判定基準の詳細は ../references/dod-verification.md を参照。
検証手順
status: done の各レポートについて：
- レポートの
task_idから対応タスクを特定queue/tasks/dev{N}.yamlを走査、または既に処理済みなら過去の発行履歴を参照
- 対応タスクの
definition_of_doneを読み込み - 各 DoD 項目について、レポートの
changesまたはartifactsに対応する記述があるか確認
判定基準（dod-verification.md から要約）:
| 基準 | 内容 |
|---|---|
| キーワード一致 | DoD 項目内のキーフレーズが changes/artifacts に現れている |
| ファイルパス類推 | DoD が言及するファイルパスが artifacts に含まれている |
| 明示マッピング | DoD と changes が同数で1対1対応している |
違反時の挙動
未カバー項目が 1件でもある 場合：
- dashboard.md の
## Notesセクションに記載（既存セクションを利用、フォーマット変更なし）- 例:
- TASK-20260201-010: DoD "ユニットテスト8件作成" が未対応（実装テスト4件のみ確認）
- 例:
- Backlog Status の該当タスクを
doneにせず、needs_review相当の扱い とする - Dev に追加作業を send-keys で指示
- PO に状況を send-keys で報告
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.
- 10d ago First seen · 262 lines · 86 tokens per session scan A 963198c123ce
sm-scan-reports is a skill published in the GitHub repository elvezjp/ixv-agents (5 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 2,862 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…
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…