Borrowing it
Nothing to install: this file belongs to atbaker/claude-draws. 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/atbaker/claude-draws/main/CLAUDE.mdgit clone --depth 1 https://github.com/atbaker/claude-drawsWrote 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/atbaker/claude-draws/claude-md)<a href="https://agentmods.dev/instructions/atbaker/claude-draws/claude-md"><img src="https://agentmods.dev/badge/instructions/atbaker/claude-draws/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.04633 | $0.04633 |
| Opus 5 | $0.02316 | $0.02316 |
| Sonnet 5 | $0.00927 | $0.00927 |
| Haiku 4.5 | $0.00463 | $0.00463 |
Grade A, and why
claude-draws 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 6d 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 — 403 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.
Project Overview
Claude Draws is an automated art project where Claude for Chrome creates crowdsourced illustrations using Kid Pix, sourced from user submissions at claudedraws.xyz. The complete workflow:
- Web form (claudedraws.xyz/submit) accepts art requests and stores them in Cloudflare D1
- Browser automation (Playwright + CDP) submits prompts to Claude for Chrome extension
- OBS recording captures the entire artwork creation process via WebSocket control
- Claude draws in a modified Kid Pix JavaScript app (served from local directory, not included in this repo)
- Temporal workflows orchestrate the post-processing pipeline
- BAML extraction parses Claude's title and artist statement from the final response
- Cloudflare R2 stores artwork images and creation videos
- Cloudflare D1 stores artwork metadata (including video URLs) in SQLite database
- SvelteKit gallery (
gallery/) displays all artworks with videos at claudedraws.xyz with SSR-on-demand - Cloudflare Workers hosts the gallery site
Repository Structure (Monorepo)
This repository uses a monorepo structure to organize different components:
claude-draws/
├── backend/ # Python backend (CLI, Temporal workflows, BAML)
│ ├── claudedraw/ # CLI tool for browser automation
│ ├── workflows/ # Temporal workflow definitions
│ ├── worker/ # Temporal worker process
│ ├── baml_src/ # BAML definitions for metadata extraction
│ ├── pyproject.toml # Python dependencies
│ └── Dockerfile.worker # Container for worker
├── gallery/ # SvelteKit frontend (SSR-on-demand with D1 API)
├── .chrome-data/ # Chrome profile for automation (gitignored)
├── downloads/ # Temporary artwork storage (gitignored)
├── docs/ # Documentation
└── docker-compose.yml # Orchestrates all services
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.
- 6d ago First seen · 403 lines · 4,633 tokens per session scan A 61ed698dc8e7
claude-draws CLAUDE.md is an instructions file published in the GitHub repository atbaker/claude-draws (11 stars, last pushed 7mo ago), licensed MIT. It adds 4,633 tokens to every session, about $0.0232 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.