coder CLAUDE.md

A project instruction file for coder/coder, a secure environment for developers and their agents. The supplied entry has no further instructions.

In plain words
What is it for?
It is intended to guide work in that project, but its concrete jobs are not described in the input.
Why use it?
There is not enough information here to identify a specific problem it removes.

Instructions file

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/coder/coder/claude-md
Clone the repo
git clone --depth 1 https://github.com/coder/coder
Per session 3 This file is loaded in full into every session.
When invoked 3 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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 $0.00003 $0.00003
Opus 5 $0.00002 $0.00002
Sonnet 5 $0.00001 $0.00001
Haiku 4.5 $0.00000 $0.00000

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

Security

Grade A, and why

coder 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 2d 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 · 1 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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. 2d ago First seen · 1 lines · 3 tokens per session scan A a54ff182c7e8

Subscribe to this mod's changes

coder CLAUDE.md is an instructions file published in the GitHub repository coder/coder (14,299 stars, last pushed 2d ago), licensed AGPL-3.0. It adds 3 tokens to every session, about $0.0000 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.

Related

Other instructions, from other repositories

codehydra CLAUDE.md

Instructions for stefanhoelzl/codehydra, covering claude.md, critical rules, no ignore comments, api/ipc interface changes and new boundary interfaces.

stefanhoelzl/codehydra · 7,616 tokens

vibeyard CLAUDE.md

Instructions for elirantutia/vibeyard, covering claude.md, what this is, build & run, testing and architecture.

elirantutia/vibeyard · 7,485 tokens

hana-developer-cli-tool-example command-documentation.instructions.md

Use when creating or updating CLI command documentation in docs/02-commands/. Generates comprehensive markdown files with Mermaid diagrams showing command flow, detailed parameter tables organized by category, syntax examples, and related commands.

SAP-samples/hana-developer-cli-tool-example · 9,187 tokens

hana-developer-cli-tool-example mcp-server-development.instructions.md

Use when creating or updating MCP (Model Context Protocol) server components. Enforces TypeScript patterns, JSON-RPC communication rules, tool/resource/prompt registration, and integration with CLI command metadata. Ensures MCP server follows protocol requirements and maintains consistency with the CLI infrastructure.

SAP-samples/hana-developer-cli-tool-example · 4,811 tokens

hana-developer-cli-tool-example route-development.instructions.md

Use when creating or updating route files in routes/. Enforces consistent structure, error handling, database connection management, internationalization, and integration with the Express server and CLI command infrastructure. Ensures routes follow established patterns for endpoint registration, response formatting…

SAP-samples/hana-developer-cli-tool-example · 5,092 tokens

hana-developer-cli-tool-example connection-pooling-timeout-management.instructions.md

Use when creating or updating code that manages database connections. Enforces consistent timeout configuration, proper connection cleanup, graceful error handling, and connection pooling best practices across CLI commands, routes, and tests.

SAP-samples/hana-developer-cli-tool-example · 3,452 tokens