jp-power-tools: Instructions file for Claude Code

AGENTS.md

jp-power-tools AGENTS.md is an instructions file for Claude Code, Codex, OpenCode from muji-j/jp-power-tools. It costs 705 tokens per session, scanned A, original, MIT.

Repository instructions for agents working on jp-power-tools, a public plugin repository for practical Japanese electricity-market work. They define source-checking, privacy, testing, and agent-routing rules.

In plain words
What is it for?
Use them when changing jp-power-tools, its Python or MCP tools, documentation, tests, dashboards, or routed coding agents.
Why use it?
They help agents use current official information, avoid exposing company data or real bidding details, and keep related project files consistent.

Instructions file for Claude CodeCodexOpenCode

Written for Claude Code and Codex and OpenCode: Claude Code plugin machinery, but also the file is AGENTS.md. Also seen: mentions AGENTS.md; mentions Codex.

This is muji-j/jp-power-tools's own configuration. It tells Claude Code, Codex and OpenCode how to work on jp-power-tools itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything jp-power-tools configures →

Reuse

Borrowing it

Nothing to install: this file belongs to muji-j/jp-power-tools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/muji-j/jp-power-tools/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/muji-j/jp-power-tools

Made for: Claude Code, Codex, OpenCode.

Wrote 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.

agentmods badge for jp-power-tools AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/muji-j/jp-power-tools/agents-md.svg)](https://agentmods.dev/instructions/muji-j/jp-power-tools/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/muji-j/jp-power-tools/agents-md"><img src="https://agentmods.dev/badge/instructions/muji-j/jp-power-tools/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 705 This file is loaded in full into every session.
When invoked 705 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00705 $0.00705
Opus 5 $0.00352 $0.00352
Sonnet 5 $0.00141 $0.00141
Haiku 4.5 $0.00071 $0.00071

Measured 7d ago against content hash c67a02e3f72c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

jp-power-tools AGENTS.md 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 7d 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.

AGENTS.md · 24 lines

What it actually says

AGENTS.md — jp-power-tools

日本の電力市場実務向けの公開・汎用 Claude/Codex プラグインリポジトリ。会社固有情報を含めず、公式公開情報と再現可能なツールだけを出荷する。

Repository Rules

  • 電力制度、数値、日程、URL は JEPX・OCCTO・METI などの最新の公式一次資料で確認する。
  • Python/MCP の既定動作は read-only とし、外部書き込み、実入札、自動提出を追加しない。生成機能は dry-run とサンプルを中心にする。
  • 回帰: cd jp-power/scripts; py -3 -m pytest tests/ -v
  • 機能変更時は README、CHANGELOG、.claude-plugin/marketplace.jsonjp-power/.claude-plugin/plugin.json、briefing/announcement の同期要否を確認する。
  • 公開リポジトリに会社名、内部 URL、実際の入札価格・数量、発電所・顧客情報を含めない。

Codex Agent Routing

  • .codex/agents/*.toml は JP シリーズ共通の Codex エージェント群であり、commonjp-office-tools とバイト単位で同一に保つ。
  • Out of scope: .claude/ (agents, settings, hooks, plugins) - never create, modify, or delete files there.
  • service_tier = "fast" 固定ロールは、範囲が限定され、結果を決定論的に検証できる作業にだけ使用する。Fast ロールが NEEDS_STANDARD を返した場合、root は適切な Standard の設計・実装・レビュー担当で同じタスクを再実行する。ユーザーは parent session で /fast on/fast off/fast status を使用でき、エージェント自身は tier を変更しない。
  • 探索=scout、設計=plan-architect、Python/MCP=script-engineer、文書=content-author、HTML=dashboard-engineer
  • 制度・数値=domain-factchecker、成果物=office-artifact-auditor、機微情報=sensitivity-auditor、仕様=spec-reviewer、テスト=test-runner、最終監査=deep-reviewer、出荷=release-engineer
  • root を含めて最大 4 threads、depth 1。実装担当と read-only reviewer を分離する。
  • ユーザーへの説明・報告はユーザーが使用した言語に合わせ、判別できない場合は日本語を使用する。コマンド、パス、識別子、公式名称は翻訳しない。
  • リモート push と release はユーザー承認後にのみ実行する。
  • Codex の変更はワークスペースルートの ../CODEX_HANDOFF.md に記録する。単独 checkout で利用できない場合は、その旨を報告する。
Changes

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.

  1. 7d ago First seen · 24 lines · 705 tokens per session scan A c67a02e3f72c

Subscribe to this mod's changes

jp-power-tools AGENTS.md is an instructions file published in the GitHub repository muji-j/jp-power-tools (1 stars, last pushed 1mo ago), licensed MIT. It adds 705 tokens to every session, about $0.0035 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.

Related

Other instructions, from other repositories

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens