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 po-request-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/po-request-yaml)<a href="https://agentmods.dev/skills/elvezjp/ixv-agents/po-request-yaml"><img src="https://agentmods.dev/badge/skills/elvezjp/ixv-agents/po-request-yaml/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/po-request-yaml"><img src="https://agentmods.dev/badge/skills/elvezjp/ixv-agents/po-request-yaml.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.00109 | $0.03629 |
| Opus 5 | $0.00055 | $0.01814 |
| Sonnet 5 | $0.00022 | $0.00726 |
| Haiku 4.5 | $0.00011 | $0.00363 |
Grade A, and why
po-request-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 11d 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 — 364 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PO Request YAML Generator
ユーザーの要望やPOの指示を受け取り、queue/po_to_sm.yaml を作成してSMに伝達する。
When to Use
ユーザーが以下のようなリクエストをした時、このスキルを実行する：
- 「〜機能を追加してほしい」
- 「〜を修正して」
- 「仕様を更新して」
- 「計画を立てて」
- 「実行して」
- 「Backlogを更新して」
- 「フィードバックを反映して」
Task Types
| task_type | 用途 | 対応フェーズ |
|---|---|---|
| constitution_update | 憲章更新タスク | 1 |
| spec_update | 仕様策定・更新タスク | 2, 7 |
| plan | 計画策定依頼 | 3 |
| execute | 実行指示 | 4 |
| verify | 検証開始指示 | 6 |
| backlog_update | Backlog更新指示 | 6 |
| feature | 機能追加（デフォルト） | - |
| bugfix | バグ修正 | - |
フェーズ順序の確認（重要）
タスク発行前に、現在のフェーズ状態を確認してください。
確認手順
po-check-constitutionでフェーズ1の完了を確認po-check-specでフェーズ2の完了を確認- 前フェーズが未完了なら、そのフェーズのタスクのみを発行
発行制限
| 現在の状態 | 発行可能なtask_type | 発行禁止 |
|---|---|---|
| フェーズ1未完了（憲章未記入） | constitution_update のみ | feature, spec_update, plan, execute 等 |
| フェーズ2未完了（仕様未反映） | spec_update のみ | feature, plan, execute 等 |
| フェーズ2完了 | 全てのtask_type | - |
禁止パターン
# ダメな例: 憲章更新と機能追加を同時に発行
# → constitution_update のみを発行し、完了後に feature を発行すること
# 1回の実行で発行するのは1タスクのみ
# 前のタスクが完了（dashboard.mdでdone確認）してから次を発行
Instructions
Step 1: task_typeの判定
ユーザー入力やコンテキストから適切なtask_typeを判定する。
判定基準:
| ユーザー入力 | task_type |
|---|---|
| 「憲章更新」「目的を記入」「constitution」 | constitution_update |
| 「仕様策定」「仕様更新」「READMEに追加」 | spec_update |
| 「計画を立てて」「設計して」「plan」 | plan |
| 「実行して」「開始して」「execute」 | execute |
| 「検証して」「検証開始」「verify」 | verify |
| 「Backlog更新」「完了にして」「ステータス変更」 | backlog_update |
| 「バグ」「不具合」「動かない」 | bugfix |
| 「機能追加」「〜したい」「〜してほしい」 | feature |
Step 2: 必要情報のヒアリング
task_typeに応じて必要な情報をヒアリングする。
共通項目:
| 項目 | 質問例 |
|---|---|
| 何を実現したいか | 「具体的にどのような動作を期待しますか？」 |
| 完了の定義 | 「どうなったらOKですか？」 |
| 優先度 | 「急ぎですか？（P0:最優先 / P1:通常 / P2:低）」 |
task_type別の追加項目:
| task_type | 追加ヒアリング |
|---|---|
| constitution_update | プロジェクトの目的・存在意義 |
| spec_update | 追加/変更する仕様の詳細 |
| plan | 対象範囲、段階的実行の必要性 |
| execute | 実行対象の計画、優先順位 |
| verify | 検証対象のリクエストID |
| backlog_update | 対象ID、新ステータス |
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.
- 11d ago First seen · 364 lines · 109 tokens per session scan A e1e550e6b66c
po-request-yaml is a skill published in the GitHub repository elvezjp/ixv-agents (5 stars, last pushed 1mo ago), licensed MIT. It adds 109 tokens to every session and 3,629 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.
remove
Remove a deployed framework or addon from the current workspace.