What is my_claude_code_setting CLAUDE.md?

A guide to a development environment containing Python and Node.js projects, cloud tools, containers, and AI coding tools.

It is for navigating the user's projects, choosing project-specific Python environments, and understanding the available shell, cloud, container, and AI tooling.

It tells a coding agent where important projects and tools are located and how the environment is configured.

my_claude_code_setting CLAUDE.md — Instructions file by workdd

Install

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.

agentmods

npx agentmods add instructions/workdd/my_claude_code_setting/claude-md

Clone the repo

git clone --depth 1 https://github.com/workdd/my_claude_code_setting

Per session 1,420 This file is loaded in full into every session.

When invoked 1,420 The same file — it is already loaded in full.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.01420	$0.01420
Opus 5	$0.00710	$0.00710
Sonnet 5	$0.00284	$0.00284
Haiku 4.5	$0.00142	$0.00142

Measured 3d ago against content hash 3f5982afc617, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

my_claude_code_setting 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 3d 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.

CLAUDE.md · 156 lines

How it starts

The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Environment Overview

This is a user home directory containing multiple projects and development tools rather than a single codebase. The environment includes:

Python development: PyCharm projects, conda, pyenv, various Python tools
Node.js development: npm, nvm, node modules
Cloud services: AWS CLI, Google Cloud SDK, Terraform
Container tools: Docker, Colima, Minikube, Kubernetes
AI/ML tools: Various LLM clients (.claude, .cursor, .continue, .gemini, .codex)

Key Project Directories

PycharmProjects/ - Python projects
ml-coding-test-prep/ - Machine learning coding practice
langfuse/ - LangFuse project directory
research-infrastructure/ - Research infrastructure code

Development Environment Setup

Shell Configuration

Primary shell: zsh (.zshrc)
Bash configuration available (.bash_profile)
Multiple PATH configurations for Python (pyenv), Node.js (nvm), and cloud CLIs

Python Environment

Multiple Python version managers: conda, pyenv
Virtual environments should be used per project
Common ML libraries appear to be installed (matplotlib, nltk, paddleocr, EasyOCR)

Node.js Environment

Managed via nvm
npm available for package management
Check individual project directories for package.json

Cloud and Infrastructure

AWS CLI configured (.aws/)
Google Cloud SDK installed in ~/google-cloud-sdk/
Kubernetes tools: kubectl, minikube (.minikube/)
Terraform available (.terraform.d/)

Working with Projects

When asked to work on code, always:

Identify which project directory contains the relevant code
Navigate to that project directory to find project-specific build/test commands
Look for project-specific configuration files (package.json, requirements.txt, Makefile, etc.)
Check for project-specific README files within those directories

Token Optimization Guidelines

Read the full file on GitHub · 156 lines

Changes

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.

3d ago First seen · 156 lines · 1,420 tokens per session scan A 3f5982afc617

Subscribe to this mod's changes

my_claude_code_setting CLAUDE.md is an instructions file published in the GitHub repository workdd/my_claude_code_setting (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 1,420 tokens to every session, about $0.0071 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.

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).

microsoft/vscode · 6,785 tokens

my_claude_code_setting CLAUDE.md