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/jujunjun110/product-starter/claude-mdgit clone --depth 1 https://github.com/jujunjun110/product-starterWrote 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/jujunjun110/product-starter/claude-md)<a href="https://agentmods.dev/instructions/jujunjun110/product-starter/claude-md"><img src="https://agentmods.dev/badge/instructions/jujunjun110/product-starter/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 | $0.01104 | $0.01104 |
| Opus 5 | $0.00552 | $0.00552 |
| Sonnet 5 | $0.00221 | $0.00221 |
| Haiku 4.5 | $0.00110 | $0.00110 |
Grade A, and why
product-starter 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 today.
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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Starter
使い方(利用者向け)
pnpm devで開発サーバーを起動pnpm verifyで品質チェック(変更後に実行)- 機能を追加したいときは Claude Code に「〇〇な機能を作って」と指示するだけでOK
- テーブルを追加したいときは「〇〇テーブルを追加して」と指示
- UIを作りたいときは「〇〇な画面を作って」と指示
- エラーが出たらエラーメッセージを貼り付けて「直して」と指示
コマンド一覧
pnpm dev # 開発サーバー起動
pnpm verify # lint → prisma generate → typecheck → unit test → depcruise
pnpm test:unit # Unit テスト
pnpm test:integration # Integration テスト(要 DATABASE_URL, INTEGRATION_TEST=true)
pnpm lint:fix # 自動フォーマット
pnpm db:migrate # DBマイグレーション作成・適用
pnpm knip # 未使用コード検出
Claude Code への指示(利用者は読まなくてOK)
アーキテクチャ
pnpm workspace monorepo。apps/webapp/ に Next.js 15 App Router アプリ。
バックエンド (src/backend/) は DDD 4層構造:
依存方向: presentation → application → domain ← infrastructure
- domain — ビジネスルール。外部依存なし。最内層
- application — UseCase。domain のみ依存(infrastructure 直接参照禁止、Gateway interface 経由)
- infrastructure — Gateway/Repository 実装。domain の interface を implements
- presentation — composition(唯一の DI ポイント、全層参照可)、loaders(読み取り)、actions(副作用)
ファイル配置ルール
src/backend/
├── domain/
│ ├── models/ # ドメインモデル (.model.ts)
│ ├── services/ # ドメインサービス (.service.ts)
│ ├── gateways/ # Gateway interface (.gateway.ts)
│ └── repositories/ # Repository interface (.repository.ts)
├── application/
│ └── usecases/ # UseCase (.usecase.ts)
├── infrastructure/
│ ├── adapters/ # Gateway 実装 (.adapter.ts) — 本番 + Stub
│ ├── repositories/ # Repository 実装 (.repository.ts)
│ └── db/ # DB接続 (prisma-client.ts)
└── presentation/
├── composition/ # DI組み立て (.composition.ts)
├── loaders/ # データ取得 (.loader.ts)
└── actions/ # 副作用 (.action.ts, 'use server')
Key Rules
- ファイル命名: kebab-case + レイヤーサフィックス
- Rich Domain Model 必須。バリデーション・生成はモデル自身のメソッドで行う
- サービス(UseCase, Domain Service)はクラスベース + コンストラクタ DI。関数エクスポート禁止
- Domain 層のエラーは
Result<T, E>型で返す。Application/Infrastructure は throw - 外部 API の Gateway は必ず Stub 実装を用意し、Composition で環境変数に応じて切り替え
index.tsバレルエクスポート禁止- API Route 原則不使用(loaders + Server Actions パターン)
- Server Component デフォルト。
'use client'は必要な場合のみ
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.
- today First seen · 94 lines · 1,104 tokens per session scan A dc44b0ee1681
product-starter CLAUDE.md is an instructions file published in the GitHub repository jujunjun110/product-starter (17 stars, last pushed 2mo ago), licensed MIT. It adds 1,104 tokens to every session, about $0.0055 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-09-03.
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).
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.
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.
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.
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).
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.