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/kstost/cokacdir/claude-mdgit clone --depth 1 https://github.com/kstost/cokacdirWrote 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/kstost/cokacdir/claude-md)<a href="https://agentmods.dev/instructions/kstost/cokacdir/claude-md"><img src="https://agentmods.dev/badge/instructions/kstost/cokacdir/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.00500 | $0.00500 |
| Opus 5 | $0.00250 | $0.00250 |
| Sonnet 5 | $0.00100 | $0.00100 |
| Haiku 4.5 | $0.00050 | $0.00050 |
Grade A, and why
cokacdir 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.
How it starts
The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You can get Rust build methods from build_manual.md file
CRITICAL: Do Not Change Design Without Permission
- NEVER change product design/UX without explicit user request
- Bug fix and design change are completely different things
- If you identify a "potential improvement" or "UX issue", only REPORT it - do NOT implement
- When user says "fix it", fix only the BUGS, not your suggestions
- If you think design change is needed, ASK FIRST before implementing
- Violating this rule wastes user's time and breaks trust
Build Guidelines
- IMPORTANT: Only build when the user explicitly requests it
- Never run build commands automatically after code changes
- Never run build commands to "verify" or "check" code
- Do not use
cargo build,python3 build.py, or any build commands unless user asks - Focus only on code modifications; user handles all builds manually
Version Management
- Version is defined in
Cargo.toml(line 3:version = "x.x.x") - All version displays use
env!("CARGO_PKG_VERSION")macro to read from Cargo.toml - To update version: only modify
Cargo.toml, all other locations reflect automatically - Never hardcode version strings in source code
Theme Color System
- All color definitions must use
Color::Indexed(number)format directly - Each UI element must have its own uniquely named color field, even if the color value is the same as another element
- Never reference another element's color (e.g., don't use
theme.bg_selectedfor viewer search input) - Define dedicated color fields in the appropriate Colors struct (e.g.,
ViewerColors.search_input_text) - Color values may be duplicated across fields, but names must be unique and semantically meaningful
Theme File Locations
- Source of truth:
src/ui/theme.rs- 테마 색상 값과 JSON 주석 모두 이 파일에서 정의 - Generated files:
~/.cokacdir/themes/*.json- 프로그램 실행 시 생성되는 사용자 설정 파일 - 테마 수정 시 반드시
src/ui/theme.rs를 수정해야 함 (생성된 JSON 파일 직접 수정 금지) - JSON 주석 형식:
"__field__": "설명"- 이 주석들도 theme.rs의to_json()함수 내에 정의됨
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 · 41 lines · 500 tokens per session scan A f70320c2a9a7
cokacdir CLAUDE.md is an instructions file published in the GitHub repository kstost/cokacdir (356 stars, last pushed yesterday), licensed MIT. It adds 500 tokens to every session, about $0.0025 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-30.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.