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 dev-receive-taskgit 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-receive-task)<a href="https://agentmods.dev/skills/elvezjp/ixv-agents/dev-receive-task"><img src="https://agentmods.dev/badge/skills/elvezjp/ixv-agents/dev-receive-task/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/dev-receive-task"><img src="https://agentmods.dev/badge/skills/elvezjp/ixv-agents/dev-receive-task.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.00082 | $0.02345 |
| Opus 5.5 | $0.00033 | $0.00938 |
| Sonnet 5.5 | $0.00016 | $0.00469 |
| Haiku 4.5 | $0.00008 | $0.00234 |
Grade A, and why
dev-receive-task 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.
Dev Receive Task
queue/tasks/dev{N}.yaml を読み取り、SPEC.md 2.3.3 スキーマに基づいてタスク内容を確認し、作業に最適なペルソナを設定する。
When to Use
- SMから send-keys で起こされた時（最初に実行するスキル）
- コンパクション復帰後にタスクを再確認する時
Instructions
Step 1: 自分の番号を確認
tmux display-message -p '#W'
| 出力 | Dev番号 | ペイン |
|---|---|---|
| dev1 | Dev1 | ixv-agents:0.2 |
| dev2 | Dev2 | ixv-agents:0.3 |
| dev3 | Dev3 | ixv-agents:0.4 |
Step 2: タスクYAML を読み取り
自分専用の queue/tasks/dev{N}.yaml を読み取る。
queue/tasks/dev1.yaml ← Dev1はこれだけ
queue/tasks/dev2.yaml ← Dev2はこれだけ
queue/tasks/dev3.yaml ← Dev3はこれだけ
他のDevのファイルは読まないこと。
Step 3: フィールドを検証
以下の必須フィールドが全て存在するか確認する：
| Field | Required | 検証ルール |
|---|---|---|
| task_id | required | TASK-YYYYMMDD-### 形式 |
| spec_ref | required | README.md または README.md#section |
| assignee | required | 自分のDev番号（dev1〜dev3） |
| type | required | dev または doc |
| summary | required | 140文字以内推奨 |
| definition_of_done | required | 1件以上 |
必須フィールドが欠けている場合: SMに status: blocked で報告する。
Step 4: タスク内容を解析
- summary から作業の全体像を把握
- definition_of_done を完了条件として明確に理解（これが合格基準）
- inputs を参照して関連ファイルや前提を確認
- outputs で期待される成果物を確認
Step 4.5: 依存タスクの状態確認（dependencies がある場合のみ）
SPEC.md §2.5.3 / §2.5.4 に基づく必須検証。dependencies が空でない場合、作業を開始する前に以下を Step として実行 すること。
詳細は ../references/dependency-validation.md を参照。
検証手順
各 dep_task_id について、queue/reports/{dep_task_id}.yaml を読み取り status を確認する。
# 例: TASK-20260201-001 の状態を確認
cat queue/reports/TASK-20260201-001.yaml | grep '^status:'
レポートが 存在しない 場合は「未着手 or in_progress」と判定する。
状態別の判定（SPEC.md §2.5.3 と同期）
| 依存先 status | Dev の対応 |
|---|---|
done |
受領可、Step 5 へ進む |
in_progress（report 不在含む） |
依存先完了まで待機、または status: blocked で報告 |
blocked |
status: blocked で再報告 |
needs_review |
status: blocked で再報告 |
| 不在（task_id 自体が存在しない） | status: blocked で報告 |
違反時の挙動
依存先のいずれかが done 以外（または不在）の場合：
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 · 82 tokens per session scan A d15a90f6ae1d
dev-receive-task is a skill published in the GitHub repository elvezjp/ixv-agents (5 stars, last pushed 2mo ago), licensed MIT. It adds 82 tokens to every session and 2,345 once invoked, about $0.0003 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…