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 creating-rulesgit 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/creating-rules)<a href="https://agentmods.dev/skills/j5ik2o/okite-ai/creating-rules"><img src="https://agentmods.dev/badge/skills/j5ik2o/okite-ai/creating-rules.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.1 | $0.00043 | $0.02309 |
| Opus 5 | $0.00022 | $0.01154 |
| Sonnet 5 | $0.00009 | $0.00462 |
| Haiku 4.5 | $0.00004 | $0.00231 |
Grade A, and why
creating-rules 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 6d 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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating Claude Code Rules
.claude/rules/ ディレクトリにモジュール化された、焦点を絞ったルールを作成する。
Quick Start
まずユーザーに確認する:
- スコープ: グローバル（全ファイル）or パス指定（特定ファイルタイプ）？
- 配置場所:
.claude/rules/（プロジェクト用）or~/.claude/rules/（個人用）？ - カテゴリ: コードスタイル、テスト、セキュリティ、API、その他？
- 対象言語/フレームワーク（該当する場合）？
次に既存ルールを確認する:
# プロジェクトのルールを確認
ls -la .claude/rules/
# 個人のルールを確認
ls -la ~/.claude/rules/
重複がないことを確認してからルールを作成する。
ルールファイルを作成:
---
paths: src/**/*.ts
---
# TypeScript Guidelines
- strict モードを使用する
- オブジェクト形状には type より interface を優先
- エクスポートされる関数には明示的な戻り値型を指定
作成前チェック
ルールを作成する前に必ず確認：
-
既存ルールの確認
ls .claude/rules/- 同じトピックのルールが存在しないか？
- 既存ルールに追記すべき内容ではないか？
-
CLAUDE.md との重複確認
- CLAUDE.md に同様の内容がないか？
- プロジェクト概要 → CLAUDE.md
- 具体的なコーディング規約 → rules/
-
スコープの適切性
- グローバルルールにすべきか、パス指定すべきか？
- 既存のパス指定ルールと競合しないか？
ルールファイル構造
グローバルルール（Frontmatter なし）
全ファイルに適用：
# Code Style
- 2スペースインデントを使用
- let より const を優先
- 未使用変数を残さない
パス指定ルール（Frontmatter あり）
Claude が一致するファイルを扱う時のみ適用：
---
paths: src/api/**/*.ts
---
# API Development Rules
- 全エンドポイントに入力バリデーションを含める
- 標準エラーレスポンス形式を使用
- OpenAPI ドキュメントコメントを含める
YAML Frontmatter
paths フィールド
単一パターン：
paths: src/**/*.ts
ブレース展開による複数パターン：
paths: src/**/*.{ts,tsx}
カンマ区切りパターン：
paths: {src,lib}/**/*.ts, tests/**/*.test.ts
Glob パターンリファレンス
| パターン | マッチ対象 |
|---|---|
**/*.ts |
任意の場所の全 TypeScript ファイル |
src/**/* |
src/ 配下の全ファイル |
*.md |
プロジェクトルート直下の Markdown ファイルのみ |
src/components/*.tsx |
特定ディレクトリ内の React コンポーネント |
**/*.{ts,tsx} |
TypeScript と TSX ファイル |
{src,lib}/**/*.ts |
src/ または lib/ 内の TypeScript |
ディレクトリ構成
基本構成
.claude/rules/
├── code-style.md # 一般的なコーディング規約
├── testing.md # テスト規約
└── security.md # セキュリティ要件
サブディレクトリあり
.claude/rules/
├── frontend/
│ ├── react.md
│ └── styles.md
├── backend/
│ ├── api.md
│ └── database.md
└── general.md
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 303 lines · 43 tokens per session scan A 1d2553c79dde
creating-rules is a skill published in the GitHub repository j5ik2o/okite-ai (81 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 2,309 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-01.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…