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-brief)<a href="https://agentmods.dev/commands/muji-j/jp-power-tools/power-brief"><img src="https://agentmods.dev/badge/commands/muji-j/jp-power-tools/power-brief/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-brief"><img src="https://agentmods.dev/badge/commands/muji-j/jp-power-tools/power-brief.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.00037 | $0.01807 |
| Opus 5 | $0.00018 | $0.00903 |
| Sonnet 5 | $0.00007 | $0.00361 |
| Haiku 4.5 | $0.00004 | $0.00181 |
Grade A, and why
power-brief 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 10d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
日本電力市場の需給ブリーフィングを収集し、自己完結型のHTMLダッシュボードとして出力する。対象: $ARGUMENTS(未指定ならエリア・日付をまず確認する)。
ライトパス(既定)
まずは power_brief_build.py によるワンショット生成を試す。手動収集(精密パス)は、これで品質不足だった系列の補強にとどめる。
- エリアを1回確認する。
power_profileの常用エリア(/power-setupで登録可)があればそれを使ってよいか確認、無ければ9エリアから選んでもらう(推測で決めない)。日付は未指定なら翌日が既定(応札判断に使う想定のため)。 - 実行する。
気象(Open-Meteo)・広域予備率(OCCTO)・スポット価格(JEPX)・停止情報(HJKS)を自動取得し、python "${CLAUDE_PLUGIN_ROOT}/scripts/power_brief_build.py" --area <エリア> [--date <YYYY-MM-DD、既定=翌日>] [--open]assets/brief-template.htmlに差し込んだ自己完結HTMLを1コマンドで生成する。 - 標準出力の**データ品質(
_quality)**を確認する。取得できなかった系列(例:weather: failed等)があれば、その系列だけ精密パスの該当手順(気象/エリア需給予報/大型電源停止/広域予備率/前日市場価格)で手動補強し、生成済みHTML中のJSONを該当部分だけ更新する。すべて成功していれば、生成物をそのままユーザーに提示する。 - 需要「予測」(各TSOの でんき予報=翌日需要想定)は
power_brief_build.pyが未取得(将来対応)のため、demand.forecast系列は精密パスの手順2で補うか、空のまま「未取得」と明記する。
精密パス
1. 準備
jp-power スキルを読み込み、references/sites.md(情報源)と references/data-sources.md(取得方法)を参照する。サイト接続・データ取得は WebFetch/WebSearch。ボット遮断対象は公式 CSV 直リンクを優先。
2. 収集(sites.md の「スポット入札前チェック順序」に従う)
- 気象 — 気象庁予報(対象エリアの府県)で気温・天気・降水確率。
- エリア需給予報 — 該当 TSO の でんき予報(対象日の需要想定・使用率・出力制御見通し)。可能なら前日実績も。
- 大型電源の停止 — HJKS で対象エリア・対象日にかかる計画/計画外停止。
- 広域予備率 — OCCTO 広域予備率Web公表システムで対象日のコマ別予備率。
- 前日市場価格 — JEPX スポットのエリアプライス(コマ別)。
3. データ整形 → DATA JSON
収集結果を下記スキーマの JSON にまとめる。48コマ分の配列(不足時は取得できたコマまで+残りは直近値で補間し、補間した旨を disclaimer に明記)。取得失敗した系列は空配列可(該当カードは非表示になる)。verdict.level と reserve の帯は予備率で決める(8%以上=good / 5〜8%=warning / 3〜5%=serious / 3%未満=critical)。
{
"area":"東京","dow":"日","date":"2026-07-12","generatedAt":"2026-07-11 18:30 JST",
"verdict":{"level":"warning","label":"ややタイト","headline":"一行の総括"},
"reserve":{"unit":"%","min":6.2,"minKoma":37,"series":[/*48個の%*/]},
"demand":{"unit":"万kW","peakKoma":37,"peakVal":5520,"forecastSource":"東京電力PG でんき予報(翌日の需要想定)","forecast":[/*48*/],"prevActual":[/*48 or []*/]},
"price":{"unit":"円/kWh","max":34.5,"maxKoma":38,"min":5.2,"avg":12.8,"series":[/*48*/]},
"risks":[{"type":"停止","sev":"serious","title":"見出し","text":"詳細"}],
"weather":{"tempMax":34,"tempMin":26,"cond":"晴れ時々くもり","pop":20,"note":"需給への含意"},
"sources":[{"name":"気象庁 予報","time":"18:10取得"}],
"disclaimer":"注意書き"
}
sevとverdict.levelはgood/warning/serious/criticalのいずれか。type(リスク種別)例: 停止 / 低予備率 / 出力制御 / 連系線 / 気象。demand.forecastSource: 需要曲線の「予測」の出所を明記する(原則、対象エリアTSOの でんき予報=翌日の需要想定。自前モデル(気象+回帰、→ calc.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.
- 10d ago First seen · 64 lines · 37 tokens per session scan A 0dc5f265581d
power-brief is a command published in the GitHub repository muji-j/jp-power-tools (1 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 1,807 once invoked, about $0.0002 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
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
init
Install the formatters this repository needs, with every command visible before it runs.
brand-generate
Generate an on-brand document from a saved Brand Profile.
genshijin-compress
A command for safely shortening Markdown or text files into the genshijin style.
adr-supersede
Create a new ADR that supersedes an existing one.
check-dev
Type-check a Z specification with fuzz.