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 agentmods add instructions/nanasess/eccube-dev-agents/claude-mdgit clone --depth 1 https://github.com/nanasess/eccube-dev-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/instructions/nanasess/eccube-dev-agents/claude-md)<a href="https://agentmods.dev/instructions/nanasess/eccube-dev-agents/claude-md"><img src="https://agentmods.dev/badge/instructions/nanasess/eccube-dev-agents/claude-md.svg" alt="Measured on agentmods" 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.01145 | $0.01145 |
| Opus 5 | $0.00573 | $0.00573 |
| Sonnet 5 | $0.00229 | $0.00229 |
| Haiku 4.5 | $0.00114 | $0.00114 |
Grade A, and why
eccube-dev-agents CLAUDE.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 5d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
概要
このリポジトリは eccube-dev-agents Claude Codeプラグインです。Git ワークフロー自動化、GitHub レビュー管理、CI ログ分析の Skills を提供します。
プラグインアーキテクチャ
Skills (plugins/eccube-dev-agents/skills/)
各 Skill は skills/<name>/SKILL.md 形式で定義。YAML フロントマターに description, allowed-tools, argument-hint を含む。
提供する Skills:
- commit - Conventional Commits 形式の日本語コミットメッセージ自動生成。複数リポジトリ対応
- commit-push-pr - コミット + Push + PR作成の一括実行。PRテンプレート自動適用対応
- review-pr - PR をレビューし、投稿せずにインラインコメントのドラフトを提示
- post-review - 確認済みドラフトを個別インラインコメントとして投稿
- validate-review - GitHub レビューコメントの妥当性検証（引数なし = 現在ブランチの PR の全コメント、PR URL 指定 = その PR の全コメント、コメント URL 指定 = 単一）
- reply-review - 確認済み GitHub レビューコメントへの一括返信
- github-logs-analyze - GitHub Actions 失敗ログの解析
- plan - Issue/PR からチェックリスト形式の実装計画を生成
レビュー系 Skill の設計原則
review-pr と post-review は「確認前に投稿しない」ことを構造で担保するために分離されている。統合や、review-pr への投稿処理の追加はこの担保を壊すため行わない。
review-pr: GitHub への POST を一切行わない（読み取り専用のghのみ）post-review: 同一会話内でreview-prが作成したドラフトのみを投稿対象とする- 指摘には
file:lineの根拠と[VERIFIED]/[ASSUMED]を付け、根拠のないものはドラフトに載せない
同じ「事前確認」の関係が validate-review → reply-review にもある。
validate-review: GitHub への書き込みを一切行わない。引数なし / PR URL 指定では対象 PR のレビューコメントを全件検証し、判定と対応方針を一覧報告するreply-review: 同一会話内でvalidate-reviewが確認したコメントのみに、スレッドごと個別に返信する
Skill 設計パターン
---
description: Skill の説明（/help に表示）
allowed-tools: Bash(git:*), Bash(gh:*), Read
argument-hint: [引数の説明]
---
# Skill のプロンプト本文
開発ワークフロー
Skill の追加/変更
plugins/eccube-dev-agents/skills/<name>/SKILL.mdを作成- YAML フロントマターで
description,allowed-toolsを定義 - プロンプト本文に手順を記述
テストとデバッグ
# プラグイン構造の確認
ls plugins/eccube-dev-agents/skills/*/SKILL.md
cat plugins/eccube-dev-agents/.claude-plugin/plugin.json
# プラグインの再インストール
claude plugin marketplace add /path/to/eccube-dev-agents
claude plugin install eccube-dev-agents
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.
- 5d ago First seen · 97 lines · 1,145 tokens per session scan A 64c4efa6f296
eccube-dev-agents CLAUDE.md is an instructions file published in the GitHub repository nanasess/eccube-dev-agents (2 stars, last pushed 1mo ago), licensed MIT. It adds 1,145 tokens to every session, about $0.0057 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 instructions, from other repositories
daisyui code_generation_with_git.instructions.md
Instructions for saadeghi/daisyui, covering activation, initial setup, development loop, error handling and session end.
planning-with-files AGENTS.md
AGENTS.md instructions for OthmanAdi/planning-with-files, covering agents.md — planning-with-files agent reference card, commit rules, release checklist (12 steps), version bump scope and changelog format.
dario CLAUDE.md
Claude Code instructions for askalf/dario, covering dario — notes for claude code (and other llm coding agents), commits and prs, style, scope and when in doubt, ask.
granite.build AGENTS.md
AGENTS.md instructions for ibm-granite/granite.build, covering agents.md, git commits, github prs and issues, project overview and common commands.
ai-git-commiter CLAUDE.md
Instructions for zdt1013/ai-git-commiter, covering ai git commiter, 项目结构, 技术栈, 常用命令 and 安装依赖.
bro-skills copilot-instructions.md
Copilot instructions for wedabro/bro-skills, covering copilot instructions for bro-skills, 1. supreme order, 2. bro-skills protocol, 3. language & code and 4. safety.