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-write-reportnpx skills add elvezjp/ixv-agents --skill dev-write-reportgit 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-write-report)<a href="https://agentmods.dev/skills/elvezjp/ixv-agents/dev-write-report"><img src="https://agentmods.dev/badge/skills/elvezjp/ixv-agents/dev-write-report.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 | $0.00084 | $0.02160 |
| Opus 5 | $0.00042 | $0.01080 |
| Sonnet 5 | $0.00017 | $0.00432 |
| Haiku 4.5 | $0.00008 | $0.00216 |
Grade A, and why
dev-write-report 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 3d 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Write Report
タスク完了後の結果を SPEC.md 2.3.4 スキーマに準拠した YAML ファイルとして queue/reports/{task_id}.yaml に書き出す。
When to Use
- タスクが完了した時（
status: done） - タスクがブロックされた時（
status: blocked） - レビューが必要な時（
status: needs_review）
Instructions
Step 1: タイムスタンプを取得
date "+%Y-%m-%dT%H:%M:%S"
必須: タイムスタンプは必ず date コマンドで取得する。推測しないこと。
Step 2: status を決定
| status | 条件 |
|---|---|
done |
definition_of_done の全項目を満たした |
blocked |
ブロッカーにより作業を継続できない |
needs_review |
作業は完了したがレビューが必要 |
注意: failed は有効な status ではない（SPEC.md 2.3.4 準拠）。
Step 2.5: Definition of Done セルフチェック（status: done を選ぶ場合）
SPEC.md §2.4.3 に基づく必須検証。status: done を選択する前に以下を Step として実行 すること。
判定基準の詳細は ../references/dod-verification.md を参照。
検証手順
対応する queue/tasks/dev{N}.yaml（または最初に受領した task）の definition_of_done を読み返し、各項目について以下を確認する。
for each item in definition_of_done:
if (item に対応する記述が changes にある) OR
(item に対応するファイルが artifacts に列挙されている):
OK
else:
未カバー項目として記録
判定基準（dod-verification.md から要約）:
| 基準 | 内容 |
|---|---|
| キーワード一致 | DoD 項目内のキーフレーズ（機能名・ファイル名・テスト名等）が changes/artifacts に現れている |
| ファイルパス類推 | DoD が言及するファイルパスが artifacts に含まれている |
| 明示マッピング | DoD と changes が同数で1対1対応している |
違反時の挙動
未カバー項目が 1件でもある 場合：
statusをdoneからneeds_reviewに格下げissuesフィールドに未カバー理由を明記- 例:
"DoD: ユニットテスト8件作成 が未対応（実装テスト4件のみ）"
- 例:
summaryにも「DoD 一部未対応」である旨を記載
status: done で報告できるのは、全 DoD 項目がカバーされている場合のみ。
例
全カバー（done で OK）:
# task の definition_of_done
- "/auth/login が POST を受け付ける"
- "ユニットテストがパスする"
# report
status: done
changes:
- "/auth/login エンドポイント実装（POST）"
- "ユニットテスト6件作成、全件パス"
artifacts:
- "src/auth/api.ts"
- "tests/auth/api.test.ts"
部分未カバー（needs_review に格下げ）:
# task の definition_of_done
- "認証 API が実装されている"
- "ユニットテスト8件作成"
# report
status: needs_review # ← done から格下げ
summary: "認証 API は実装完了。DoD 一部未対応のため要レビュー。"
changes:
- "認証 API を実装"
artifacts:
- "src/auth/api.ts"
issues:
- "DoD: ユニットテスト8件作成 が未対応"
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.
- 3d ago First seen · 225 lines · 84 tokens per session scan A 002d9fc6a44d
dev-write-report is a skill published in the GitHub repository elvezjp/ixv-agents (5 stars, last pushed 25d ago), licensed MIT. It adds 84 tokens to every session and 2,160 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…