init-configurator: Instructions file for Claude Code

CLAUDE.md

init-configurator CLAUDE.md is an instructions file for Claude Code from Stepkar2004/init-configurator. It costs 755 tokens per session, scanned A, original, MIT.

A project instruction file for Claude Code describing the project's constitution, rules, skills, and file locations. Claude Code is a coding assistant that follows repository instructions while working on files.

In plain words
What is it for?
Use it to guide coding work, identify which skills apply, run required validation gates, and record missing guidance in the designated project file.
Why use it?
It gives the assistant shared project context so its changes follow the repository's required workflow, checks, and organization.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md.

This is Stepkar2004/init-configurator's own configuration. It tells Claude Code how to work on init-configurator itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything init-configurator configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Stepkar2004/init-configurator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Stepkar2004/init-configurator/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/Stepkar2004/init-configurator

Made for: Claude Code.

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

agentmods badge for init-configurator CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/stepkar2004/init-configurator/claude-md/github.svg)](https://agentmods.dev/instructions/stepkar2004/init-configurator/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/stepkar2004/init-configurator/claude-md"><img src="https://agentmods.dev/badge/instructions/stepkar2004/init-configurator/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for init-configurator CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/stepkar2004/init-configurator/claude-md"><img src="https://agentmods.dev/badge/instructions/stepkar2004/init-configurator/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 755 This file is loaded in full into every session.
When invoked 755 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00755 $0.00755
Opus 5.5 $0.00302 $0.00302
Sonnet 5.5 $0.00151 $0.00151
Haiku 4.5 $0.00076 $0.00076

Measured 2mo ago against content hash 41077e3edd53, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

init-configurator 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 2mo 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 · 49 lines

How it starts

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

init-configurator — constitution

Consult the skill index before acting. Skills carry the HOW; each fires by shape:

  • workflow — any code written, changed, or resumed: the SWE loop (orient → plan → implement → verify → document → commit, NEVER push → reflect). Its references cover scaling past one context and rot-checking. Start here when unsure what to do next.
  • bootstrap — phase 0: starting, scaffolding, or adopting a project or stack.
  • skill-manager — skill hygiene and the genome's lifecycle: a lesson landing, a skill added/split/merged, genes moving between repos. References: evolve, absorb, authoring.
  • socials — posting, launching, promoting, or making anything findable. The human always posts. References: LinkedIn, GitHub, visuals.

Working without a matching skill? Log one line in docs/state/miss-log.md, keep working.

The line: skills know HOW, tools know WHETHER, project.yaml records WHAT. Never move knowledge from markdown into code constants.

The rules (binding, not style)

  • Gates all green before every commit — the set CI runs: ruff check, ruff format --check, mypy src, pytest --cov (≥90%), initc lint-paths, initc validate, and the schema-drift check. project.yaml declares the core tasks (initc run test | lint | typecheck); the pre-commit and CI configs are the full set.
  • Commit at chunk boundaries; NEVER push. The user pushes, or explicitly says push. Public repo: an unpushed mistake is free, a pushed one is not.
  • A skill edit is a code change — reviewed diff, never silent. This constitution grows only when the user confirms it; a lesson learned goes through evolve into a skill.
  • The user owns every line. Public showcase repo — code quality is the product; nothing merges that the user cannot explain. Approving fast without understanding is a bug: slow down.
  • Root-relative paths only (initc lint-paths enforces it); no global installs (deps live in ./.venv). The env rule: the same turn code first reads a new var, declare it in project.yaml and re-run initc env — doctor's env-sync fails on drift.
  • Post drafts live in docs/posts/ (gitignored). No em dashes (U+2014) in post text.

Read the full file on GitHub · 49 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.

  1. 2mo ago First seen · 49 lines · 755 tokens per session scan A 41077e3edd53

Subscribe to this mod's changes

init-configurator CLAUDE.md is an instructions file published in the GitHub repository Stepkar2004/init-configurator (1 stars, last pushed 3mo ago), licensed MIT. It adds 755 tokens to every session, about $0.0030 per session on Opus 5.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.

Related

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

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens