Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add muji-j/jp-power-tools/plugin install jp-powerWrote 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/commands/muji-j/jp-power-tools/power-verify)<a href="https://agentmods.dev/commands/muji-j/jp-power-tools/power-verify"><img src="https://agentmods.dev/badge/commands/muji-j/jp-power-tools/power-verify/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/commands/muji-j/jp-power-tools/power-verify"><img src="https://agentmods.dev/badge/commands/muji-j/jp-power-tools/power-verify.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.00056 | $0.00888 |
| Opus 5 | $0.00028 | $0.00444 |
| Sonnet 5 | $0.00011 | $0.00178 |
| Haiku 4.5 | $0.00006 | $0.00089 |
Grade A, and why
power-verify 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 9d 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.
What it actually says
jp-power スキル本体（配布しているナレッジファイル）の情報鮮度を点検する。利用者の入札データ・実績データ等を検証するコマンドではない（そちらは /power-get 等で取得したデータを直接確認する）。範囲: $ARGUMENTS（未指定なら all）。
本スキルは汎用配布用のため、URL・数値・制度が古いと信頼が崩れる。定期（推奨: 半期に1回）または制度改正の情報を得た際に実行する。
手順
1. sites（URL生存確認）— 範囲 sites|all
references/sites.mdの全 URL を WebFetch で接続確認する。ボット遮断(403)はサイト稼働の有無のみ判定（ブラウザ型 UA の観点）。- リダイレクト/404/ドメイン消滅を洗い出し、「URL移転の罠」表に反映する候補を挙げる。
2. numbers（数値・制度確認）— 範囲 numbers|all
references/markets.mdの時刻・締切・インバランスのアンカー値など主要数値を公式ソース（sites.md 第8節: エネ庁・EGC・OCCTO・EPRX）と突合する。- 特に施行予定の制度（例: インバランス補正料金の上限改正）が既に施行済みか、値が変わっていないかを確認する。
3. calendar（年間日程確認）— 範囲 calendar|all
references/markets.mdの年間カレンダー（容量市場オークション、供給計画の取りまとめ等）の日程が当該年度の公式発表と一致するか確認する。
出力（変更提案書）
| ファイル | 項目 | 現在値 | 確認結果 | 対応 |
- 対応 = 「有効」／「要更新（新値）」／「要再確認」。
- 一つでも更新が必要なら: ① 該当参照ファイルを修正 ② バージョン表記（plugin.json）を更新 ③ 変更履歴（CHANGELOG）に記録。
- 最後に点検日を sites.md 冒頭の「URL検証」日付へ反映することを提案する。
原則
- 実接続・公式文書に基づいてのみ判定する。記憶で「大丈夫」と判断しない。
- 変更はユーザー確認後に適用（自動修正の前にまず提案書を提示）。
制度変更の検知（power_watch 連携）
python "${CLAUDE_PLUGIN_ROOT}/scripts/power_watch.py" --allで公式公表物の一覧を取得。- 新規/最近の公表物が markets.md の数値・年間日程・sites.md のURL に関係しそうなら、「○○が変わった可能性 → 該当参照ファイルの該当箇所を確認」と更新候補を提示（自動修正はしない）。
- 例: 需給調整市場・容量市場・インバランス関連の回次が出ていれば markets.md の該当数値を要再確認。
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.
- 9d ago First seen · 37 lines · 56 tokens per session scan A 303509408e4c
power-verify is a command published in the GitHub repository muji-j/jp-power-tools (1 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 888 once invoked, about $0.0003 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 commands, from other repositories
research
Professional equity research analysis with institutional-grade formatting.
close-review
Month-end close / GL compliance check — invokes accounting-reviewer to produce TM-accounting-{slug}.md with double-entry integrity, ASC 606 revenue-recognition, period-lock, and SOX ITGC gaps.
procurement-review
Procurement / source-to-pay compliance check — invokes procurement-reviewer to produce TM-procurement-{slug}.md with three-way match, segregation-of-duties, OFAC-screening, and SOX procurement-controls gaps.
tax-review
Tax-filing compliance check — invokes tax-reviewer to produce TM-tax-{slug}.md with MeF e-file schema, Form 8879, PTIN/Circular 230, and IRC §7216 consent gaps.
compare
Compare two or more payment providers head to head for a concrete situation — real fees on a real amount, coverage, onboarding time, and what PagoKit can actually build for each.
add
Add a second payment provider alongside an existing integration, without touching the one already running.