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 skills/jujunjun110/product-starter/add-featurenpx skills add jujunjun110/product-starter --skill add-featuregit 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/skills/jujunjun110/product-starter/add-feature)<a href="https://agentmods.dev/skills/jujunjun110/product-starter/add-feature"><img src="https://agentmods.dev/badge/skills/jujunjun110/product-starter/add-feature.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.00038 | $0.00748 |
| Opus 5 | $0.00019 | $0.00374 |
| Sonnet 5 | $0.00008 | $0.00150 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
add-feature 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.
What it actually says
機能追加スキル
ユーザーが「〇〇な機能を作って」と指示したときに適用する。 DDD 4層アーキテクチャに従い、以下のファイルを一括生成する。
生成するファイル
-
Domain Model (
src/backend/domain/models/{name}.model.ts)- Rich Domain Model として設計(ファクトリメソッド
create()+reconstruct()) - バリデーションはモデル自身で行う
- エラーは
Result<T, E>型で返す
- Rich Domain Model として設計(ファクトリメソッド
-
Repository Interface (
src/backend/domain/repositories/{name}.repository.ts)- ドメインモデル型のみ使用(ORM型を出さない)
-
Gateway Interface(必要な場合:
src/backend/domain/gateways/{name}.gateway.ts)- 外部API連携がある場合のみ
-
UseCase (
src/backend/application/usecases/{action}-{name}.usecase.ts)- クラスベース + コンストラクタ DI
execute()メソッドで公開
-
Repository 実装 (
src/backend/infrastructure/repositories/prisma-{name}.repository.ts)- Prisma 経由。ORM型 ↔ ドメインモデル変換を担当
-
Gateway 実装(必要な場合)
- 本番:
src/backend/infrastructure/adapters/{provider}-{name}.adapter.ts - Stub:
src/backend/infrastructure/adapters/stub-{name}.adapter.ts
- 本番:
-
Composition (
src/backend/presentation/composition/{name}.composition.ts)- DI組み立て。環境変数でStub/本番を切り替え
-
Loader (
src/backend/presentation/loaders/{name}.loader.ts)- データ取得用
-
Action (
src/backend/presentation/actions/{name}.action.ts)'use server'付き。副作用用
-
ページ (
src/app/{path}/page.tsx)- Server Component。loader を呼んでデータ表示
-
Unit テスト
test/unit/domain/models/{name}.model.test.tstest/unit/application/usecases/{action}-{name}.usecase.test.ts
Prisma スキーマ
必要に応じて prisma/schema.prisma にモデルを追加し、pnpm db:migrate でマイグレーションを作成する。
ルール
- ファイル命名は kebab-case + レイヤーサフィックス
- 依存方向: presentation → application → domain ← infrastructure
- application から infrastructure を直接 import しない
- presentation/loaders, actions から domain, infrastructure を直接 import しない
- 関数エクスポートでサービスを実装しない(クラスベース必須)
- 生成後に
pnpm verifyを実行して全パスすることを確認
サンプル(参考)
既存の Joke 機能(joke.model.ts, generate-joke.usecase.ts 等)を参考にする。
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 · 66 lines · 38 tokens per session scan A 9ae16e26d5bb
add-feature is a skill published in the GitHub repository jujunjun110/product-starter (17 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 748 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…