Borrowing it
Nothing to install: this file belongs to 477-Studio/claude-gym. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/477-Studio/claude-gym/main/CLAUDE.mdgit clone --depth 1 https://github.com/477-Studio/claude-gymWrote 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/477-studio/claude-gym/claude-md)<a href="https://agentmods.dev/instructions/477-studio/claude-gym/claude-md"><img src="https://agentmods.dev/badge/instructions/477-studio/claude-gym/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.1 | $0.01062 | $0.01062 |
| Opus 5 | $0.00531 | $0.00531 |
| Sonnet 5 | $0.00212 | $0.00212 |
| Haiku 4.5 | $0.00106 | $0.00106 |
Grade A, and why
claude-gym 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 8d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Build Commands
go build -o cgym . # Build binary for current platform
./cgym # Watch current project's Claude conversations
./cgym watch ~/path/to/project # Watch specific project
./cgym replay <jsonl-file> # Replay a conversation file
# Studio mode - asset development with hot reload (not included in release)
go build -tags debug -o cgym . && ./cgym studio
Build Requirements
- CGO_ENABLED=1 (Raylib needs C bindings)
- Linux deps: libgl1-mesa-dev, libxi-dev, libxcursor-dev, libxrandr-dev, libxinerama-dev, libxxf86vm-dev, libwayland-dev, libxkbcommon-dev
Architecture
Claude Gym is an exercise reminder companion for Claude Code users. It watches JSONL conversation logs and prompts the user to do exercises during natural pause points (plan mode, permission escalations). Features a pixel-art developer character in a home office biome.
Core Components
main.go - Entry point with CLI parsing (watch, replay, studio subcommands). Contains the main game loop, AppState, and event handling.
menu.go - State machine for the exercise flow: Idle → Menu → Prompting → PumpUp → Exercising → StopConfirm → Summary. Handles all keyboard input per mode. Exercise mode is fully isolated — no external events can interrupt it.
exercises.go - Exercise config loader. Reads exercises.json for exercise definitions (name, animation row, reps, bubble text).
animations.go - Animation state machine managing animation types: Idle, CoffeeSip, Wave, PumpUp, ChairDips, ArmCircles. Each has frame timing, loop mode, and optional completion callbacks.
watcher.go - File watcher that monitors ~/.claude/projects/[encoded-path]/*.jsonl. Parses JSON lines, extracts events, and emits typed Event structs through a channel. Supports live tailing and replay modes.
Renderer Architecture
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.
- 8d ago First seen · 99 lines · 1,062 tokens per session scan A 49246305d1b5
claude-gym CLAUDE.md is an instructions file published in the GitHub repository 477-Studio/claude-gym (42 stars, last pushed 6mo ago), licensed MIT. It adds 1,062 tokens to every session, about $0.0053 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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).
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.
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.