claude-code AGENTS.md

A repository instruction file for Claude Code, an AI coding tool. It defines the Python setup, required code-quality checks, testing process, and rules for handling type errors.

In plain words
What is it for?
Use it when changing the project to set up Python with uv, format and check the code, run type checks, and run the test suite in the required order.
Why use it?
It reduces inconsistent environments and makes failures visible before code is merged.

Instructions file for CodexOpenCode

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/pushpenderrathore/claude-code/agents-md
Clone the repo
git clone --depth 1 https://github.com/Pushpenderrathore/claude-code

Made for: Codex, OpenCode.

Per session 943 This file is loaded in full into every session.
When invoked 943 The same file — it is already loaded in full.
Security scan C 2 findings. Scan, not verified.
Origin 78% copy Near-identical to another mod 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.00943 $0.00943
Opus 5 $0.00472 $0.00472
Sonnet 5 $0.00189 $0.00189
Haiku 4.5 $0.00094 $0.00094

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

Security

Grade C, and why

claude-code AGENTS.md scanned grade C with 2 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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

- Install astral uv using "curl -LsSf https://astral.sh/uv/install.sh | sh" if not already installed and if already installed then update it to the latest version

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- Install astral uv using "curl -LsSf https://astral.sh/uv/install.sh | sh" if not already installed and if already installed then update it to the latest version
Origin

This is a copy

78% identical to free-claude-code AGENTS.md — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

AGENTS.md · 55 lines

How it starts

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

AGENTIC DIRECTIVE

This file is identical to CLAUDE.md. Keep them in sync.

CODING ENVIRONMENT

  • Install astral uv using "curl -LsSf https://astral.sh/uv/install.sh | sh" if not already installed and if already installed then update it to the latest version
  • Install Python 3.14 using uv python install 3.14 if not already installed
  • Always use uv run to run files instead of the global python command.
  • Current uv ruff formatter is set to py314 which has supports multiple exception types without paranthesis (except TypeError, ValueError:)
  • Read .env.example for environment variables.
  • All CI checks must pass; failing checks block merge.
  • Add tests for new changes (including edge cases), then run uv run pytest.
  • Run checks in this order: uv run ruff format, uv run ruff check, uv run ty check, uv run pytest.
  • Do not add # type: ignore or # ty: ignore; fix the underlying type issue.
  • All 5 checks are enforced in tests.yml on push/merge (parallel jobs: suppression grep, ruff-format, ruff-check, ty, pytest).
  • Branch protection: set required status checks to all of those statuses (e.g. Ban type ignore suppressions, ruff-format, ruff-check, ty, pytest—use the exact labels GitHub shows, which may be prefixed with CI /). Remove ci from required checks if it was previously added for the old gate job.

IDENTITY & CONTEXT

  • You are an expert Software Architect and Systems Engineer.
  • Goal: Zero-defect, root-cause-oriented engineering for bugs; test-driven engineering for new features. Think carefully; no need to rush.
  • Code: Write the simplest code possible. Keep the codebase minimal and modular.

ARCHITECTURE PRINCIPLES

  • Shared utilities: Put shared Anthropic protocol logic in neutral core/anthropic/ modules. Do not have one provider import from another provider's utils.
  • DRY: Extract shared base classes to eliminate duplication. Prefer composition over copy-paste.
  • Encapsulation: Use accessor methods for internal state (e.g. set_current_task()), not direct _attribute assignment from outside.
  • Provider-specific config: Keep provider-specific fields (e.g. nim_settings) in provider constructors, not in the base ProviderConfig.
  • Dead code: Remove unused code, legacy systems, and hardcoded values. Use settings/config instead of literals (e.g. settings.provider_type not "nvidia_nim").
  • Performance: Use list accumulation for strings (not += in loops), cache env vars at init, prefer iterative over recursive when stack depth matters.
  • Platform-agnostic naming: Use generic names (e.g. PLATFORM_EDIT) not platform-specific ones (e.g. TELEGRAM_EDIT) in shared code.
  • No type ignores: Do not add # type: ignore or # ty: ignore. Fix the underlying type issue.
  • Complete migrations: When moving modules, update imports to the new owner and remove old compatibility shims in the same change unless preserving a published interface is explicitly required.
  • Maximum Test Coverage: There should be maximum test coverage for everything, preferably live smoke test coverage to catch bugs early

Read the full file on GitHub · 55 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. 2d ago First seen · 55 lines · 943 tokens per session scan C 57b483cb4d61

Subscribe to this mod's changes

claude-code AGENTS.md is an instructions file published in the GitHub repository Pushpenderrathore/claude-code (2 stars, last pushed 1mo ago), licensed MIT. It adds 943 tokens to every session, about $0.0047 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). It is 78% identical to free-claude-code AGENTS.md, differing in 12 lines, and is treated as a copy.

Related

Other instructions, from other repositories

PlanExe AGENTS.md

Instructions for PlanExeOrg/PlanExe, covering planexe agent instructions, repo architecture map, shared contracts, hard rules (agent safety) and environment variables.

PlanExeOrg/PlanExe · 1,637 tokens

AI-Healthcare-System AGENTS.md

AGENTS.md instructions for pavanbadempet/AI-Healthcare-System, covering agents.md - ai healthcare system, session start, instruction architecture, repo map and always true.

pavanbadempet/AI-Healthcare-System · 1,804 tokens

AI-Healthcare-System copilot-instructions.md

Copilot instructions for pavanbadempet/AI-Healthcare-System, a project described as: AI Data Engineering Healthcare Platform: PySpark Medallion Lakehouse, Airflow DAGs, 5 ML Models, Local LLM RAG, and FastAPI Clinical Architecture.

pavanbadempet/AI-Healthcare-System · 208 tokens

AI-Healthcare-System frontend.instructions.md

Instructions for pavanbadempet/AI-Healthcare-System, a project described as: AI Data Engineering Healthcare Platform: PySpark Medallion Lakehouse, Airflow DAGs, 5 ML Models, Local LLM RAG, and FastAPI Clinical Architecture.

pavanbadempet/AI-Healthcare-System · 171 tokens

AI-Healthcare-System backend.instructions.md

Instructions for pavanbadempet/AI-Healthcare-System, a project described as: AI Data Engineering Healthcare Platform: PySpark Medallion Lakehouse, Airflow DAGs, 5 ML Models, Local LLM RAG, and FastAPI Clinical Architecture.

pavanbadempet/AI-Healthcare-System · 124 tokens

AI-Healthcare-System tests.instructions.md

Instructions for pavanbadempet/AI-Healthcare-System, a project described as: AI Data Engineering Healthcare Platform: PySpark Medallion Lakehouse, Airflow DAGs, 5 ML Models, Local LLM RAG, and FastAPI Clinical Architecture.

pavanbadempet/AI-Healthcare-System · 91 tokens