free-claude-code CLAUDE.md

Project instructions for Free Claude Code covering its coding workflow, Python environment, formatting, type checking, tests, and continuous integration. Continuous integration is automated checking that runs before code is merged.

In plain words
What is it for?
Setting up the project, running Python through uv, formatting code, checking types, adding tests, and running local CI before pushing changes.
Why use it?
They make the development process consistent and prevent changes from bypassing required checks or tests.

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/alishahryar1/free-claude-code/claude-md
Clone the repo
git clone --depth 1 https://github.com/Alishahryar1/free-claude-code
Per session 2,226 This file is loaded in full into every session.
When invoked 2,226 The same file — it is already loaded in full.
Security scan C 2 findings. Scan, not verified.
Origin 100% 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.02226 $0.02226
Opus 5 $0.01113 $0.01113
Sonnet 5 $0.00445 $0.00445
Haiku 4.5 $0.00223 $0.00223

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

Security

Grade C, and why

free-claude-code CLAUDE.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 yesterday.

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

100% identical to free-claude-code AGENTS.md — 0 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.

CLAUDE.md · 110 lines

How it starts

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

AGENTIC DIRECTIVE

Keep AGENTS.md and CLAUDE.md identical.

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.0 stable using uv python install 3.14.0 if not already installed (requires uv >=0.9; see [tool.uv] required-version in pyproject.toml)
  • 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).
  • Before pushing, prefer ./scripts/ci.sh (macOS/Linux) or .\scripts\ci.ps1 (Windows) to run the local CI sequence; requires uv on PATH. The local scripts run Ruff in repair mode (ruff format, then ruff check --fix) before type checking and tests.
  • Use --only / --skip (PowerShell: -Only / -Skip) to run a subset when iterating; use --dry-run to print commands without running them.
  • GitHub CI remains check-only for Ruff (ruff format --check, ruff check) so branch protection verifies committed code.
  • Fall back to individual repair commands when debugging local failures: uv run ruff format, uv run ruff check --fix, uv run ty check, uv run pytest -v --tb=short. Use GitHub-style checks only when verifying enforcement locally: uv run ruff format --check, uv run ruff check.
  • Do not add # type: ignore or # ty: ignore; fix the underlying type issue.
  • Do not add from __future__ import annotations; Python 3.14 native lazy annotations are the project standard.
  • All 6 check IDs are represented in scripts/ci.sh / scripts/ci.ps1 and enforced by tests.yml before each merge (parallel jobs: suppression grep, ruff-format, ruff-check, ty, pytest, playwright).
  • Deterministic rendered Admin UI interactions live under e2e/ and run separately from ordinary pytest. Install Chromium once with uv run playwright install chromium; API and unit contracts remain under tests/.
  • GitHub CI runs for every pull request, including stacked PRs targeting non-main branches. Head updates trigger fresh checks; strict required checks keep PRs targeting main current with main, so the tested PR tree is the tree squash-merged without a duplicate post-merge run.
  • A separate trusted Dependency Cache workflow runs after pushes to main only and is the sole writer for reusable Python and uv dependency caches. Pull-request jobs only restore caches; the maintenance workflow never reruns validation and is not a required status check.
  • Repository protection should use rulesets: a non-bypassable main integrity ruleset requires pull requests and strict required checks, keeps branches current, and blocks direct/force pushes to main; a separate review ruleset may allow Alishahryar1/admins to bypass review only.
  • Required status checks: set required status checks to all of those statuses (e.g. Ban suppressions and legacy annotations, ruff-format, ruff-check, ty, pytest, playwright—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.

Read the full file on GitHub · 110 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. yesterday First seen · 110 lines · 2,226 tokens per session scan C 2b267e1faed3

Subscribe to this mod's changes

free-claude-code CLAUDE.md is an instructions file published in the GitHub repository Alishahryar1/free-claude-code (51,809 stars, last pushed yesterday), licensed MIT. It adds 2,226 tokens to every session, about $0.0111 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 100% identical to free-claude-code AGENTS.md, differing in 0 lines, and is treated as a copy.

Related

Other instructions, from other repositories

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.

openai/codex · 5,182 tokens

buildNext

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 · 6,785 tokens

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.

vercel/next.js · 7,296 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit 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.

github/spec-kit · 7,040 tokens

langchain 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,345 tokens