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/stepkar2004/init-configurator/claude-mdgit clone --depth 1 https://github.com/Stepkar2004/init-configuratorWrote 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/stepkar2004/init-configurator/claude-md)<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="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.00755 | $0.00755 |
| Opus 5 | $0.00378 | $0.00378 |
| Sonnet 5 | $0.00151 | $0.00151 |
| Haiku 4.5 | $0.00076 | $0.00076 |
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 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.
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.yamldeclares 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-pathsenforces it); no global installs (deps live in ./.venv). The env rule: the same turn code first reads a new var, declare it inproject.yamland re-runinitc env— doctor's env-sync fails on drift. - Post drafts live in
docs/posts/(gitignored). No em dashes (U+2014) in post text.
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 · 49 lines · 755 tokens per session scan A 41077e3edd53
init-configurator CLAUDE.md is an instructions file published in the GitHub repository Stepkar2004/init-configurator (1 stars, last pushed 1mo ago), licensed MIT. It adds 755 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
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.