mcp-gauge: Command for Claude Code

.claude/commands/setup-project.md

setup-project is a command for Claude Code from sogawa-yk/mcp-gauge. It costs 0 tokens per session (983 once invoked), scanned A, a copy of setup-project, MIT.

A command for creating the six main project documents from existing ideas or an interactive discussion. These documents describe the product requirements, design, architecture, repository structure, development rules, and terms.

In plain words
What is it for?
Use it when starting a project that needs documented requirements, functional and technical designs, coding guidelines, a repository plan, and a glossary.
Why use it?
It turns scattered ideas into a shared set of project documents. The process pauses for approval after creating the product requirements document.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is sogawa-yk/mcp-gauge's own configuration. It tells Claude Code how to work on mcp-gauge 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 mcp-gauge configures →

Reuse

Borrowing it

Nothing to install: this file belongs to sogawa-yk/mcp-gauge. 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/sogawa-yk/mcp-gauge/main/.claude/commands/setup-project.md
Clone the repo
git clone --depth 1 https://github.com/sogawa-yk/mcp-gauge

Made for: Claude Code.

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 setup-project

README.md
[![agentmods](https://agentmods.dev/badge/commands/sogawa-yk/mcp-gauge/setup-project/github.svg)](https://agentmods.dev/commands/sogawa-yk/mcp-gauge/setup-project)
Your own site
<a href="https://agentmods.dev/commands/sogawa-yk/mcp-gauge/setup-project"><img src="https://agentmods.dev/badge/commands/sogawa-yk/mcp-gauge/setup-project/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.

agentmods 80×15 button for setup-project

Your own site · 80×15
<a href="https://agentmods.dev/commands/sogawa-yk/mcp-gauge/setup-project"><img src="https://agentmods.dev/badge/commands/sogawa-yk/mcp-gauge/setup-project.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 983 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.00000 $0.00983
Opus 5 $0.00000 $0.00491
Sonnet 5 $0.00000 $0.00197
Haiku 4.5 $0.00000 $0.00098

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

Security

Grade A, and why

setup-project 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.

Origin

This is a copy

100% identical to setup-project — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/setup-project.md · 110 lines

What it actually says

初回プロジェクトセットアップ

このコマンドは、プロジェクトの6つの永続ドキュメントを対話的に作成します。

実行方法

claude
> /setup-project

実行前の確認

docs/ideas/ ディレクトリ内のファイルを確認します。

# 確認
ls docs/ideas/

# ファイルが存在する場合
✅ docs/ideas/initial-requirements.md が見つかりました
   この内容を元にPRDを作成します

# ファイルが存在しない場合
⚠️  docs/ideas/ にファイルがありません
   対話形式でPRDを作成します

手順

ステップ0: インプットの読み込み

  1. docs/ideas/ 内のマークダウンファイルを全て読む
  2. 内容を理解し、PRD作成の参考にする

ステップ1: プロダクト要求定義書の作成

  1. prd-writingスキルをロード
  2. docs/ideas/の内容を元にdocs/product-requirements.mdを作成
  3. 壁打ちで出たアイデアを具体化:
    • 詳細なユーザーストーリー
    • 受け入れ条件
    • 非機能要件
    • 成功指標
  4. ユーザーに確認を求め、承認されるまで待機

以降のステップはプロダクト要求定義書の内容を元にするため、自動的に作成する

ステップ2: 機能設計書の作成

  1. functional-designスキルをロード
  2. docs/product-requirements.mdを読む
  3. スキルのテンプレートとガイドに従ってdocs/functional-design.mdを作成

ステップ3: アーキテクチャ設計書の作成

  1. architecture-designスキルをロード
  2. 既存のドキュメントを読む
  3. スキルのテンプレートとガイドに従ってdocs/architecture.mdを作成

ステップ4: リポジトリ構造定義書の作成

  1. repository-structureスキルをロード
  2. 既存のドキュメントを読む
  3. スキルのテンプレートに従ってdocs/repository-structure.mdを作成

ステップ5: 開発ガイドラインの作成

  1. development-guidelinesスキルをロード
  2. 既存のドキュメントを読む
  3. スキルのテンプレートに従ってdocs/development-guidelines.mdを作成

ステップ6: 用語集の作成

  1. glossary-creationスキルをロード
  2. 既存のドキュメントを読む
  3. スキルのテンプレートに従ってdocs/glossary.mdを作成

完了条件

  • 6つの永続ドキュメントが全て作成されていること

完了時のメッセージ:

「初回セットアップが完了しました!

作成したドキュメント:
✅ docs/product-requirements.md
✅ docs/functional-design.md
✅ docs/architecture.md
✅ docs/repository-structure.md
✅ docs/development-guidelines.md
✅ docs/glossary.md

これで開発を開始する準備が整いました。

今後の使い方:
- ドキュメントの編集: 普通に会話で依頼してください
  例: 「PRDに新機能を追加して」「architecture.mdを見直して」

- 機能の追加: /add-feature [機能名] を実行してください
  例: /add-feature ユーザー認証

- ドキュメントレビュー: /review-docs [パス] を実行してください
  例: /review-docs docs/product-requirements.md
」
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. 9d ago First seen · 110 lines · 0 tokens per session scan A f9724bb5656e

Subscribe to this mod's changes

setup-project is a command published in the GitHub repository sogawa-yk/mcp-gauge (0 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 983 tokens. A static security scan graded it A with 0 findings. It is 100% identical to setup-project, differing in 0 lines, and is treated as a copy.