masayan-uni-code-plugins CLAUDE.md

Repository instructions for masayan1126’s collection of Claude Code plugins. They describe the required marketplace, README, command, and skill files when adding a plugin.

In plain words
What is it for?
Use them when creating or updating a plugin in the repository. They cover the expected directory structure, manifest entries, command files, and English and Japanese README updates.
Why use it?
Adding a plugin involves several connected files, and missing one can leave the marketplace or documentation incomplete. These instructions make those update requirements explicit.

Instructions file

Install

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.

agentmods
npx agentmods add instructions/masayan1126/masayan-uni-code-plugins/claude-md
Clone the repo
git clone --depth 1 https://github.com/masayan1126/masayan-uni-code-plugins
Per session 643 This file is loaded in full into every session.
When invoked 643 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00643 $0.00643
Opus 5 $0.00321 $0.00321
Sonnet 5 $0.00129 $0.00129
Haiku 4.5 $0.00064 $0.00064

Measured 2d ago against content hash 38b73f54ee18, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

masayan-uni-code-plugins 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 2d 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.

CLAUDE.md · 81 lines

What it actually says

CLAUDE.md - masayan-uni-plugins

プラグイン追加時の必須作業

新しいスキルをプラグインとして追加する際は、以下の2つのファイルを必ず更新すること:

1. .claude-plugin/marketplace.json

plugins配列に新しいプラグインのエントリを追加:

{
  "name": "プラグイン名",
  "description": "説明",
  "version": "1.0.0",
  "author": { "name": "masayan" },
  "source": "./plugins/プラグイン名",
  "category": "development"
}

2. README.mdREADME_ja.md(ルート)

両方のREADMEファイルを必ず更新すること:

  • README.md(英語版): 「Available Plugins」テーブルに追加
  • README_ja.md(日本語版): 「利用可能なプラグイン」テーブルに追加
<!-- README.md -->
| [プラグイン名](./plugins/プラグイン名) | Description in English | バージョン |

<!-- README_ja.md -->
| [プラグイン名](./plugins/プラグイン名) | 日本語の説明 | バージョン |

重要: README.mdを修正する場合は、必ずREADME_ja.mdも同時に修正すること。

プラグインの構造

各プラグインは plugins/ ディレクトリ配下に作成し、最低限以下の構成とする:

plugins/プラグイン名/
├── .claude-plugin/
│   └── plugin.json
├── commands/
│   └── 動詞-対象.md
└── skills/
    └── スキル名/
        └── SKILL.md

スキルとコマンドのセット

スキルを追加する際は、必ず対応するコマンドファイルも作成すること。

1. plugin.json に commands ディレクトリを指定

{
  "commands": "./commands/"
}

2. commands/ ディレクトリにコマンドファイルを作成

ファイル名がスラッシュコマンド名になる(例: fetch-ai-news.md/fetch-ai-news

---
description: コマンドの説明
---

Execute the skill at `skills/スキル名` to ...

コマンド名のルール:

  • 動詞で開始する(例: create-, generate-, fetch-, scan-, convert-, extract-
  • ケバブケース(小文字とハイフン)を使用
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. 2d ago First seen · 81 lines · 643 tokens per session scan A 38b73f54ee18

Subscribe to this mod's changes

masayan-uni-code-plugins CLAUDE.md is an instructions file published in the GitHub repository masayan1126/masayan-uni-code-plugins (5 stars, last pushed 5mo ago), licensed MIT. It adds 643 tokens to every session, about $0.0032 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

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

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

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,182 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,345 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

next.js 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