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/edo1z/claude-cli.nvim/claude-mdgit clone --depth 1 https://github.com/edo1z/claude-cli.nvimWrote 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/edo1z/claude-cli.nvim/claude-md)<a href="https://agentmods.dev/instructions/edo1z/claude-cli.nvim/claude-md"><img src="https://agentmods.dev/badge/instructions/edo1z/claude-cli.nvim/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.00768 | $0.00768 |
| Opus 5 | $0.00384 | $0.00384 |
| Sonnet 5 | $0.00154 | $0.00154 |
| Haiku 4.5 | $0.00077 | $0.00077 |
Grade A, and why
claude-cli.nvim 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 4d 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.
What it actually says
Claude Code Multi-Instance Manager 開発ガイド
重要事項
開発プロセス
- TDD(テスト駆動開発): t-wada流のTDDで開発を進める
- Red: 失敗するテストを書く
- Green: テストを通す最小限の実装
- Refactor: コードを改善
- コミット粒度: 機能単位で小まめにコミット
- 品質保証:
- コミット前に全てのテストがパスすることを確認
- テストをパスさせるための無益な修正は行わない
- LSPツールで修正したファイルをチェックし、エラー・警告を修正
- コミット後:
/compactを実行
テスト方針
- 全てのコードにユニットテストを作成
- テストフレームワーク: Plenary Busted を使用
- テストファイルは
spec/ディレクトリに配置 - ファイル名は
*_spec.luaの形式
コーディング規約
- Luaのコーディングスタイルに従う
- モジュール間の疎結合を維持
- エラーハンドリングを徹底
- 非同期処理にはvim.loopを使用
Git管理
- 現在のブランチ:
feature/tmux-manager - コミットは機能単位で細かく行う
- プッシュは明示的に指示があるまで行わない
実装の進め方
docs/implementation-plan.mdの計画に従って進める- 各タスク完了時に計画書の進捗を更新
- 実装前に既存コードの構造を理解する
- テストを同時に作成する
ディレクトリ構造
claude-cli.nvim/
├── lua/
│ ├── claude-cli/ # 既存のCLI管理
│ ├── claude-prompt/ # 既存のプロンプト管理
│ └── claude-manager/ # 新規:マネージャーモジュール
│ ├── init.lua # メインマネージャー
│ ├── tmux.lua # tmuxセッション管理
│ ├── ui_list.lua # 一覧画面UI
│ ├── ui_individual.lua # 個別ウィンドウUI
│ └── state.lua # 状態管理
├── spec/ # テストディレクトリ
│ └── claude-manager/
│ ├── tmux_spec.lua
│ ├── ui_list_spec.lua
│ ├── ui_individual_spec.lua
│ └── ...
└── docs/
├── multi-instance-manager-design.md
└── implementation-plan.md
参考リンク
- 設計書:
/docs/multi-instance-manager-design.md - 実装計画:
/docs/implementation-plan.md - 参考実装: https://github.com/edo1z/nvim-tmux-test
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.
- 4d ago First seen · 68 lines · 768 tokens per session scan A 9bc461cfcc5a
claude-cli.nvim CLAUDE.md is an instructions file published in the GitHub repository edo1z/claude-cli.nvim (10 stars, last pushed 1y ago), licensed MIT. It adds 768 tokens to every session, about $0.0038 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
nvim-mcp CLAUDE.md
Claude Code instructions for linw1995/nvim-mcp, covering claude.md, project overview, development commands, building and running and development build and run.
sidekick.nvim AGENTS.md
Instructions for folke/sidekick.nvim, covering agent cheat sheet, project overview, everyday commands, adding features and writing tests.
opencode.nvim AGENTS.md
Instructions for nickjvandyke/opencode.nvim, covering opencode.nvim — agent guide, what it is, entrypoints, config quirks and dependencies.
agentic.nvim AGENTS.md
Instructions for carlos-algms/agentic.nvim, covering agents guide, nested instructions, skill driven, domain glossary — lazy read and architectural decisions (adrs) — optional read.
agentic.nvim CLAUDE.md
Instructions for carlos-algms/agentic.nvim: CRITICAL See @AGENTS.md for Instructions, it's the source of truth for all my instructions, no exceptions, it should be read and be part of your context before any other action.
claude-code.nvim CLAUDE.md
Instructions for greggh/claude-code.nvim, covering project: claude code plugin, essential commands, project structure, current focus and multi-instance support.