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-verify-acceptancegit 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-verify-acceptance)<a href="https://agentmods.dev/skills/elvezjp/ixv-agents/po-verify-acceptance"><img src="https://agentmods.dev/badge/skills/elvezjp/ixv-agents/po-verify-acceptance/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-verify-acceptance"><img src="https://agentmods.dev/badge/skills/elvezjp/ixv-agents/po-verify-acceptance.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.00111 | $0.01852 |
| Opus 5 | $0.00056 | $0.00926 |
| Sonnet 5 | $0.00022 | $0.00370 |
| Haiku 4.5 | $0.00011 | $0.00185 |
Grade A, and why
po-verify-acceptance 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PO Verify Acceptance
SMの検証結果報告と仕様(README.md)に基づき、実装結果を検証・判断する。
When to Use
- SMから検証結果の報告を受けた時
- 「受入確認」「検証」「acceptance」と言われた時
- ワークフロー フェーズ6(検証・受入フェーズ)時
前提
このスキルを実行する前に、以下が完了していること:
po-request-yamlでtask_type: verifyを発行済み- SMが計画(docs/)と仕様(README.md)に基づき成果物を検証済み
- SMからPOに検証結果が報告済み
Instructions
Step 1: SMの検証結果を確認
SMから報告された検証結果を確認する。
確認項目:
- SMが検証した計画書(docs/)の内容
- SMが検証した仕様(README.md)との整合性
- 各受入基準に対する検証結果(OK/NG)
- 問題点・懸念事項
Step 2: 受入基準の取得
README.md から対象リクエストに関連する受入基準を取得:
- Acceptance Criteria セクションを確認
- 対象リクエストに関連する項目を抽出
Step 3: 仕様に基づく検証・判断
SMの報告内容を仕様(README.md)と照合し、POとして判断する:
| 受入基準 | SM検証結果 | PO判断 |
|---|---|---|
| 基準A | OK | OK |
| 基準B | NG(理由) | NG |
| 基準C | OK(懸念あり) | 要確認 |
Step 4: 結果に基づくアクション
問題なし(全基準達成)の場合:
検証完了: 全ての受入基準を満たしています。
リクエストID: {request_id}
検証結果: OK (N/N 基準達成)
SM検証結果:
{SMの検証結果サマリ}
PO判断:
| 受入基準 | SM検証 | PO判断 | 備考 |
|---------|--------|--------|------|
| 基準A | OK | OK | {evidence} |
| 基準B | OK | OK | {evidence} |
→ 次のステップ:
1. Human に受入の承認を依頼してください
2. 承認後、po-request-yaml(task_type: backlog_update)でBacklog更新を指示
問題あり(基準未達成)の場合:
検証完了: 一部の受入基準を満たしていません。
リクエストID: {request_id}
検証結果: NG (M/N 基準達成)
SM検証結果:
{SMの検証結果サマリ}
PO判断:
| 受入基準 | SM検証 | PO判断 | 備考 |
|---------|--------|--------|------|
| 基準A | OK | OK | {evidence} |
| 基準B | NG | NG | {reason} |
→ 次のステップ:
1. Human に問題を報告してください
2. 5.3 設計計画フェーズへ差し戻し
SMの検証報告がない場合:
検証不可: SMからの検証結果報告がありません。
リクエストID: {request_id}
→ 次のステップ:
1. po-request-yaml(task_type: verify)で検証開始をSMに依頼してください
Examples
Example 1: 問題なし
SMの検証結果報告:
- 計画(docs/auth-plan.md)に基づき検証
- 認証画面の表示: OK(E2Eテスト通過)
- ログイン後の遷移: OK(E2Eテスト通過)
README.md の Acceptance Criteria:
## Acceptance Criteria
- ログインボタンをクリックすると認証画面が表示される
- 正しい認証情報でログインするとダッシュボードに遷移する
報告:
検証完了: 全ての受入基準を満たしています。
リクエストID: REQ-20260201-001
検証結果: OK (2/2 基準達成)
SM検証結果:
計画(docs/auth-plan.md)に基づき検証。全項目E2Eテスト通過。
PO判断:
| 受入基準 | SM検証 | PO判断 | 備考 |
|---------|--------|--------|------|
| ログインボタンをクリックすると認証画面が表示される | OK | OK | E2Eテスト通過 |
| 正しい認証情報でログインするとダッシュボードに遷移する | OK | OK | E2Eテスト通過 |
→ 次のステップ:
1. Human に受入の承認を依頼してください
2. 承認後、po-request-yaml(task_type: backlog_update)でBacklog更新を指示
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 · 199 lines · 111 tokens per session scan A ba210feb4f28
po-verify-acceptance is a skill published in the GitHub repository elvezjp/ixv-agents (5 stars, last pushed 1mo ago), licensed MIT. It adds 111 tokens to every session and 1,852 once invoked, about $0.0006 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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.