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-write-task-yamlgit 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-write-task-yaml)<a href="https://agentmods.dev/skills/elvezjp/ixv-agents/sm-write-task-yaml"><img src="https://agentmods.dev/badge/skills/elvezjp/ixv-agents/sm-write-task-yaml.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.00090 | $0.03256 |
| Opus 5 | $0.00045 | $0.01628 |
| Sonnet 5 | $0.00018 | $0.00651 |
| Haiku 4.5 | $0.00009 | $0.00326 |
Grade A, and why
sm-write-task-yaml 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 8d 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 — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SM Write Task YAML
タスク分解の結果を SPEC.md 2.3.3 スキーマに準拠した YAML ファイルとして queue/tasks/dev{N}.yaml に書き出す。
When to Use
- Phase 3: 調査・検討タスクをDevに依頼する時
- Phase 4: 実装タスクを分解してDevに割り当てる時
- Phase 5: 追加タスクが発生した時
Instructions
Step 1: task_id を採番
- 既存の
queue/tasks/配下のYAMLファイルを確認 - 今日の日付で
TASK-YYYYMMDD-###形式のIDを採番 - 同日に複数タスクがある場合は連番をインクリメント
# タイムスタンプ取得（必須: 推測しないこと）
date "+%Y-%m-%dT%H:%M:%S"
Step 2: Dev の空き状況を確認
タスク割り当て前に、各Devの空き状況を確認する。
# Dev1の状態確認
tmux capture-pane -t ixv-agents:0.2 -p | tail -20
# Dev2の状態確認
tmux capture-pane -t ixv-agents:0.3 -p | tail -20
# Dev3の状態確認
tmux capture-pane -t ixv-agents:0.4 -p | tail -20
状態判定:
| 表示 | 状態 |
|---|---|
❯ / bypass permissions on |
idle（割り当て可能） |
thinking / Esc to interrupt / Effecting… |
busy（割り当て不可） |
Step 3: タスク分解（5つの問い）
タスクをDevに振る前に、必ず以下を自問する：
| # | 問い | 考えるべきこと |
|---|---|---|
| 1 | 目的分析 | ユーザーが本当に欲しいものは何か？成功基準は何か？ |
| 2 | タスク分解 | どう分解すれば最も効率的か？並列可能か？依存関係は？ |
| 3 | 人数決定 | 分割可能なら複数Devに分散。無意味な分割はしない |
| 4 | 観点設計 | レビューならペルソナ・シナリオ。開発なら専門性 |
| 5 | リスク分析 | RACE-001の恐れは？Devの空き状況は？依存関係の順序は？ |
Step 4: RACE-001 チェック
同一ファイル書き込み禁止:
❌ 禁止: Dev1 → output.md / Dev2 → output.md（競合）
✅ 正しい: Dev1 → output_1.md / Dev2 → output_2.md
| 条件 | 判断 |
|---|---|
| 成果物が複数ファイルに分かれる | 分割して並列投入 |
| 作業内容が独立している | 分割して並列投入 |
| 前工程の結果が次工程に必要 | 順次投入 |
| 同一ファイルへの書き込みが必要 | 1名で実行 |
Step 5: YAML を生成
SPEC.md 2.3.3 スキーマに準拠したYAMLを生成する。
schema_version: "1.0"
created_at: "YYYY-MM-DDTHH:MM:SSZ"
updated_at: "YYYY-MM-DDTHH:MM:SSZ"
task_id: "TASK-YYYYMMDD-###"
spec_ref: README.md
request_id: "REQ-YYYYMMDD-###"
assignee: "dev1"
type: "dev"
summary: "140文字以内のタスク概要"
definition_of_done:
- "完了条件1"
- "完了条件2"
inputs:
- "参照ファイルや前提"
outputs:
- "期待成果物"
dependencies:
- "TASK-..."
Step 5.5: タスク発行前の検証
SPEC.md §2.4.2 / §2.4.4 / §2.5 に基づく必須検証。書き込み前に以下を Step として実行 すること。
依存検証の詳細は ../references/dependency-validation.md を参照。
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.
- 8d ago First seen · 308 lines · 90 tokens per session scan A 20e1373b3312
sm-write-task-yaml is a skill published in the GitHub repository elvezjp/ixv-agents (5 stars, last pushed 1mo ago), licensed MIT. It adds 90 tokens to every session and 3,256 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.