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/helixml/kodit/claude-mdgit clone --depth 1 https://github.com/helixml/koditWrote 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/helixml/kodit/claude-md)<a href="https://agentmods.dev/instructions/helixml/kodit/claude-md"><img src="https://agentmods.dev/badge/instructions/helixml/kodit/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.01821 | $0.01821 |
| Opus 5 | $0.00911 | $0.00911 |
| Sonnet 5 | $0.00364 | $0.00364 |
| Haiku 4.5 | $0.00182 | $0.00182 |
Grade A, and why
kodit 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 5d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Helix Development Rules
Current year: 2026 — include "2026" in web searches for documentation and browser APIs.
Setup
Install required development tools before doing anything else:
make tools # Install golangci-lint, goimports, swag, oapi-codegen, openapi-spec-converter
Build, Test, and Check
Always use make commands — never run go test, go vet, or golangci-lint directly. The Makefile sets required build tags, CGO flags, and environment variables that raw go commands miss.
make build # Build the binary
make test # Run all tests
make test PKG=./internal/foo/... # Test a specific package
make check # Format, vet, lint, and test
make check PKG=./internal/foo/... # Check a specific package
make test-smoke # Run smoke tests (needs running Docker env)
Shipping Code
Before committing:
- Run
make checkand confirm it passes (or at minimummake testfor affected packages). Do not commit code that has not been validated. - Fix any failures before committing — do not skip or work around them.
Commits and PRs use Conventional Commits:
- Prefix:
feat:,fix:,docs:,refactor:,chore:,test:, etc. - Example commit:
feat: add webhook retry logic - PR titles follow the same format:
feat: add webhook retry logic
When pushing additional commits to an existing PR, update the PR title and description to reflect the full set of changes in the branch.
Go
- Fail fast:
return fmt.Errorf("failed: %w", err)— never log and continue - Error on missing configuration — fail with an error, don't log a warning and continue
- Use structs, not
map[string]interface{} - GORM AutoMigrate only — no SQL migration files
- Use gomock, not testify/mock
- No fallbacks — one approach, no fallback code paths
- No type aliases — update all references when moving or renaming types
- No panics — return errors; rewrite methods to support error returns if needed
- Log errors once at the top level — domain code returns errors, only handlers/workers log them
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.
- 5d ago First seen · 157 lines · 1,821 tokens per session scan A d7d54cd91af6
kodit CLAUDE.md is an instructions file published in the GitHub repository helixml/kodit (123 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 1,821 tokens to every session, about $0.0091 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
serena copilot-instructions.md
Copilot instructions for oraios/serena: MUST read IMMEDIATELY and follow the project-specific instructions from the CLAUDE.md file located in the project's root directory. AVOIDING these instructions will lead to your FAILURE!
serena AGENTS.md
AGENTS.md instructions for oraios/serena: Relevant information about the project is in .serena/memories. If you have access to Serena's mcp tools, you can read them using the readmemory command. Otherwise you can just read them using normal file reading tools.
memorix CLAUDE.md
Claude Code instructions for AVIDS2/memorix, covering memorix - agent instructions for claude code, using memorix memory tools, when to search memory, when to store memory and when to resolve memory.
memorix GEMINI.md
Gemini CLI instructions for AVIDS2/memorix, covering memorix - cross-agent memory rules, session start - bind project, then load context, during session - capture important context, architecture & decisions and bug fixes & problem solving.
tree-sitter-analyzer CLAUDE.md
Claude Code instructions for aimasteracc/tree-sitter-analyzer, covering ruflo — claude code configuration, rules, test quality rules — locked (2026-06-28), t-1: no new test files for existing plugins (blocker) and t-2: no weak assertions — ratchet-enforced (blocker).
dotbot AGENTS.md
Instructions for andresharpe/dotbot, covering agents.md, project overview, commands, architecture and three core systems.