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-receive-requestgit 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-receive-request)<a href="https://agentmods.dev/skills/elvezjp/ixv-agents/sm-receive-request"><img src="https://agentmods.dev/badge/skills/elvezjp/ixv-agents/sm-receive-request/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-receive-request"><img src="https://agentmods.dev/badge/skills/elvezjp/ixv-agents/sm-receive-request.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.00079 | $0.03593 |
| Opus 5.5 | $0.00032 | $0.01437 |
| Sonnet 5.5 | $0.00016 | $0.00719 |
| Haiku 4.5 | $0.00008 | $0.00359 |
Grade A, and why
sm-receive-request 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 — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SM Receive Request
POからの指示（queue/po_to_sm.yaml）を読み取り、task_type に基づいて適切なフェーズを判定し、フェーズ別のアクション指示を返す。
When to Use
- POからの send-keys で起こされた時
- コンパクション復帰後に現在の指示を確認する時
- ワークフローサイクルの開始時
Instructions
Step 1: po_to_sm.yaml を読み取り
queue/po_to_sm.yaml を読み取り、以下のフィールドを確認する：
| フィールド | 確認内容 |
|---|---|
| task_type | フェーズ判定の基準 |
| request_id | リクエスト追跡用 |
| priority | 優先度（P0/P1/P2） |
| summary | 要件概要 |
| acceptance_criteria | 受入条件 |
Step 1.5: 受領時の必須項目検証
SPEC.md §2.4.2 / §2.4.4 に基づく必須検証。Step 2 に進む前に以下を Step として実行 すること。
検証1: 必須フィールド欠落チェック（SPEC.md §2.4.4）
task_type / request_id / summary / acceptance_criteria のいずれかが欠落している場合：
処理を保留
PO に send-keys で確認:
「po_to_sm.yaml の {field} が欠落しています。確認してください。」
検証2: acceptance_criteria 空配列チェック（SPEC.md §2.4.2）
acceptance_criteria が 空配列 の場合：
処理を保留
PO に send-keys で確認:
「acceptance_criteria が空です。受入条件を最低1件記入してください。」
これは PO 側の po-request-yaml でも検証されるべきだが、SM 側でも二重に確認することで取りこぼしを防ぐ。
違反時の挙動
| 違反内容 | アクション |
|---|---|
| 必須フィールド欠落 | PO に send-keys で確認、処理を保留（Step 2 に進まない） |
acceptance_criteria 空 |
PO に send-keys で確認、処理を保留 |
priority 欠落のみ |
P1 をデフォルトとして処理、dashboard.md の ## Notes に注記 |
検証をすべてパスした場合のみ、Step 2 に進む。
Step 2: task_type からフェーズを判定
SPEC.md §2.6 に基づくフェーズ判定。task_type の種別に応じて以下のいずれかのルートで判定する。
Step 2-A: 直接マッピング（SPEC.md §2.6.1）
task_type が以下のいずれかの場合、対応フェーズに直接マッピングする。
| task_type | Phase | Dashboard表記 | 次スキル/アクション |
|---|---|---|---|
constitution_update |
1 | 工程1 Constitution — 原則決定 |
sm-update-spec |
spec_update |
2 | 工程2 Specify — 企画・要件定義 |
sm-update-spec |
plan |
3 | 工程3 Plan — 設計計画 |
複雑さ判断 → sm-write-task-yaml or docs/作成 → sm-update-spec |
execute |
4 | 工程4 Tasks — タスク分割 |
sm-write-task-yaml |
verify |
6 | 工程6 Verify/Accept — 検証・受入 |
成果物検証 → PO通知 |
backlog_update |
6 | 工程6 Verify/Accept — 検証・受入 |
sm-update-spec |
Step 2-B: 決定木による判定（SPEC.md §2.6.2、feature / bugfix の場合）
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 · 345 lines · 79 tokens per session scan A 06d0efd8868f
sm-receive-request is a skill published in the GitHub repository elvezjp/ixv-agents (5 stars, last pushed 2mo ago), licensed MIT. It adds 79 tokens to every session and 3,593 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,"…