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/kaze-jp/kusa/claude-mdgit clone --depth 1 https://github.com/kaze-jp/kusaWrote 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/kaze-jp/kusa/claude-md)<a href="https://agentmods.dev/instructions/kaze-jp/kusa/claude-md"><img src="https://agentmods.dev/badge/instructions/kaze-jp/kusa/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.1 | $0.01991 | $0.01991 |
| Opus 5 | $0.00996 | $0.00996 |
| Sonnet 5 | $0.00398 | $0.00398 |
| Haiku 4.5 | $0.00199 | $0.00199 |
Grade A, and why
kusa 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 5d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kusa - AI開発者のためのMarkdownエディター
プロジェクト概要
AI開発時代にMarkdownを読む/書く/レビューする体験を再定義する、軽量・高速なMarkdownエディター&ビューワー。
ビジョン
"Ghosttyがターミナル体験を再定義したように、kusaがMarkdown体験を再定義する"
ターゲットユーザー
- ターミナルAI開発者(Claude Code, Cursor CLI, Kiro CLI ユーザー)
- VS Codeを開かずに開発する層
- Markdown中心の開発ワークフロー(spec, plan, CLAUDE.md, AGENTS.md, PR review)
技術スタック
- Frontend: SolidJS + TypeScript
- Backend: Rust (Tauri v2)
- Markdown: unified/remark ecosystem
- Editor: CodeMirror 6 + vim extension
- Styling: Tailwind CSS
- Build: bun
アーキテクチャ方針
- Tauri v2 でネイティブウィンドウ + WebView
- CLI起動:
kusa ./file.mdorkusa .(ディレクトリ) - 軽量: Electron不使用、Chromium同梱なし
- 3つのモード: Preview / Edit / Split (プレビュー+エディタ並列)
コアコンセプト
- Instant Open — CLI引数、ファイルドロップ、パイプで即起動
- Vim-First — CodeMirror vim mode。jk escape、Space leader
- Beautiful Preview — GitHub風レンダリング + シンタックスハイライト
- AI Context Aware — CLAUDE.md, AGENTS.md, .cursorrules のシンタックス対応
- Terminal Native — Ghostty/Warp/iTerm のファイルリンクから起動
MVP機能 (v0.1)
- Markdownファイルのプレビュー表示
- CodeMirror vim mode での編集
- Split view (エディター左 + プレビュー右)
- CLI起動 (
kusa file.md) - ファイルのドラッグ&ドロップ
- GitHub Flavored Markdown 対応
- ダークテーマ
- ファイル保存 (auto-save + manual)
v0.2以降
- GitHub PR連携 (
kusa pr 123) - Diff表示 (2ファイル比較)
- AIコンテキストファイルのバリデーション
- 複数ファイルタブ
- ファイルツリー (オプショナル)
- カスタムテーマ
- mermaid / KaTeX 対応
開発ルール
- bun を使用
- コミットメッセージは Conventional Commits
- Rust側は最小限に保つ(ファイルI/O、CLI、OS連携のみ)
- UI/ロジックはなるべくフロントエンドに寄せる
- 実装は SDD フェーズ (Phase 1-5) に従う
- CodeRabbit レビュー必須(Phase 4)
git commit --no-verify禁止
SDD (Spec-Driven Development) — powered by konbini
本プロジェクトは konbini (SDD + Agent Orchestrator) で開発する。
プリセット: solo-full-auto — 上流承認後は完全自律実行。
ワークフロー概要
設計: /kiro:spec-init → /kiro:spec-requirements → /kiro:spec-design → /kiro:spec-tasks
実装: /kiro:ao-run <feature> → 自律実行 (実装→テスト→PR→レビュー→マージ)
kiro コマンド一覧
| コマンド | 説明 |
|---|---|
/kiro:spec-init <desc> |
Spec初期化 |
/kiro:spec-requirements <feature> |
要件生成 (EARS形式) |
/kiro:spec-design <feature> [-y] |
技術設計生成 |
/kiro:spec-tasks <feature> [-y] |
実装タスク生成 |
/kiro:spec-impl <feature> [tasks] |
TDD実装実行 |
/kiro:ao-run <feature> |
AO 自律実行 (実装〜マージ) |
/kiro:spec-status [feature] |
進捗確認 |
/kiro:validate-design <feature> |
設計レビュー |
/kiro:validate-impl [feature] |
実装バリデーション |
/kiro:validate-gap <feature> |
ギャップ分析 |
/kiro:steering |
ステアリング管理 |
/kiro:steering-custom |
カスタムステアリング作成 |
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.
- 5d ago First seen · 160 lines · 1,991 tokens per session scan A 20965cb273bb
kusa CLAUDE.md is an instructions file published in the GitHub repository kaze-jp/kusa (2 stars, last pushed 3mo ago), licensed MIT. It adds 1,991 tokens to every session, about $0.0100 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-08-31.
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.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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).