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 skills add j5ik2o/okite-ai --skill repository-designgit clone --depth 1 https://github.com/j5ik2o/okite-aiWrote 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/j5ik2o/okite-ai/repository-design)<a href="https://agentmods.dev/skills/j5ik2o/okite-ai/repository-design"><img src="https://agentmods.dev/badge/skills/j5ik2o/okite-ai/repository-design/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.
<a href="https://agentmods.dev/skills/j5ik2o/okite-ai/repository-design"><img src="https://agentmods.dev/badge/skills/j5ik2o/okite-ai/repository-design.svg" alt="Reviewed on agentmods" width="80" 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.00240 | $0.02481 |
| Opus 5 | $0.00120 | $0.01241 |
| Sonnet 5 | $0.00048 | $0.00496 |
| Haiku 4.5 | $0.00024 | $0.00248 |
Grade A, and why
repository-design 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 7d 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Design
リポジトリは集約のI/Oに特化した責務である。
設計原則
命名規則
リポジトリ名は 集約名 + Repository でなければならない。
# NG: テーブル名ベース
OrdersTableRepository
UserAccountsRepository (テーブル名 user_accounts に由来)
# NG: DTOベース
OrderDtoRepository
UserResponseRepository
# OK: 集約名ベース
OrderRepository
UserRepository
検出基準: リポジトリ名に Table, Dto, Entity, Record, Row 等のインフラ用語が含まれている。
CQS(Command Query Separation)
リポジトリのメソッドはCQSに従う。各メソッドはコマンド(状態変更、戻り値なし)またはクエリ(状態変更なし、値を返す)のいずれかである。
Query(問い合わせ): 集約を返す。副作用なし。
Command(命令): 集約を受け取り、voidを返す。状態を変更する。
単件・複数件I/O
単件I/O:
// Query: 単件取得
fun findById(id: OrderId): Order?
// Command: 単件保存
fun store(order: Order)
複数件I/O:
// Query: 複数件取得
fun findByIds(ids: List<OrderId>): List<Order>
// Command: 複数件保存
fun storeMulti(orders: List<Order>): Int
同期・非同期パターン
リポジトリは同期型・非同期型いずれでも設計できる。エラーは例外方式またはResult/Either方式を選択する。
エラー方式の詳細な設計指針は error-handling スキルを参照。
同期型(例外方式):
// Query: 例外でエラーを通知
fun findById(id: OrderId): Order?
// Command
fun store(order: Order)
同期型(Result/Either方式):
// Query: Result型でエラーを返す
fun findById(id: OrderId): Result<Order?, RepositoryError>
// Command
fun store(order: Order): Result<Unit, RepositoryError>
非同期型(Future):
// Query: Futureのエラー機構を使用
def findById(id: OrderId): Future[Option[Order]]
// Command
def store(order: Order): Future[Unit]
非同期型(async/await + Result):
// Query
async fn find_by_id(&self, id: &OrderId) -> Result<Option<Order>, RepositoryError>;
// Command
async fn store(&self, order: &Order) -> Result<(), RepositoryError>;
アンチパターン
findByIdの戻り値が集約でない
// NG: DTOを返す
fun findById(id: OrderId): OrderDto
// NG: テーブル行を返す
fun findById(id: OrderId): OrderRecord
// NG: エンティティの一部を返す
fun findById(id: OrderId): OrderSummary
// OK: 集約を返す
fun findById(id: OrderId): Order?
ドメインロジックを含むメソッド名
リポジトリは集約のI/O(保存・取得・削除)のみを担う。ドメイン固有の操作をメソッド名に含めてはならない。
// NG: ドメインロジックがリポジトリに漏れている
fun leave(userId: UserId) // 「退会」はドメインの振る舞い
fun activate(orderId: OrderId) // 「有効化」はドメインの振る舞い
fun cancel(orderId: OrderId) // 「キャンセル」はドメインの振る舞い
fun approve(requestId: RequestId) // 「承認」はドメインの振る舞い
fun rename(userId: UserId) // 「名前の変更」はドメインの振る舞い
// NG: DB操作を想起するメソッド名(リポジトリはDB以外の実装もありえるため)
fun insert(order: Order) // INSERT文を連想
fun update(order: Order) // UPDATE文を連想
fun select(id: OrderId): Order? // SELECT文を連想
fun upsert(order: Order) // UPSERT文を連想
// OK: コレクションとしてのI/O操作
fun store(user: User)
fun put(order: Order)
fun add(order: Order)
fun delete(order: Order)
fun findById(id: OrderId): Order?
fun storeMulti(orders: List<Order>): Int
fun putAll(orders: List<Order>)
fun addAll(orders: List<Order>)
fun findByIds(ids: List<OrderId>): List<Order>
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.
- 7d ago First seen · 262 lines · 240 tokens per session scan A 54e9deb7b45d
repository-design is a skill published in the GitHub repository j5ik2o/okite-ai (81 stars, last pushed 4mo ago), licensed MIT. It adds 240 tokens to every session and 2,481 once invoked, about $0.0012 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
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
convex-explain-app
Explain an existing Convex app — data model + relationships, public vs internal functions, auth/ownership model, components, a request→data flow — read from the schema and function surface. Read-only.
platform-custom-field-generate
Use this skill when users need to create, generate, or validate Salesforce Custom Field metadata. Trigger when users mention custom fields, field types, Roll-up Summary fields, Master-Detail relationships, Lookup relationships, formula fields, picklists, dependent (controlling) picklists, referencing a value set from…
durable-objects
Build, debug, or review Cloudflare Durable Objects code for persistent state and coordination.
field-service-sobject-create-configure
Headless 360 REST API deployment step for creating sObject records. Handles describe-based field discovery, required-field derivation, entity-relationship ordering, and composite graph transactions. Use this skill when a designer skill (or a user directly) needs to create sObject records after design confirmation…
nornicdb-grpc
Drive NornicDB over gRPC — the Qdrant-compatible surface (Collections, Points, Snapshots) plus the additive NornicSearch service. Use when ingesting via Qdrant SDKs, migrating from Qdrant, or running hybrid text+vector search from a non-Bolt client. Covers connection, RPC catalog, collection→database mapping…