basecamp CLAUDE.md

basecamp CLAUDE.md is an instructions file for coding agents from janmaaarc/basecamp. It costs 2,252 tokens per session, scanned A, original, MIT.

A project guide for coding agents working on Basecamp, covering project defaults, frontend rules, coding practices, security, and how to verify completed work.

In plain words
What is it for?
Building or changing the project, applying its file and dependency rules, checking security concerns, and verifying work before shipping.
Why use it?
It gives the agent consistent decisions and quality checks for a codebase whose exact tools and defaults may vary.

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/janmaaarc/basecamp/claude-md
Clone the repo
git clone --depth 1 https://github.com/janmaaarc/basecamp
Per session 2,252 This file is loaded in full into every session.
When invoked 2,252 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original 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.02252 $0.02252
Opus 5 $0.01126 $0.01126
Sonnet 5 $0.00450 $0.00450
Haiku 4.5 $0.00225 $0.00225

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

Security

Grade A, and why

basecamp 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 3d 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 · 164 lines

How it starts

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

@RTK.md @rules/karpathy.md @rules/security.md

Rule priority: security rules override simplicity rules. When they conflict, default to the secure choice.

About You

  • I build [e.g. AI agents, web apps, automation tools]
  • Stack: [e.g. Next.js, Python, Supabase, Node.js]
  • I value production-ready code over quick hacks.

Your Defaults

  • Package manager: [npm / pnpm / yarn / pip]
  • Auth: [Supabase Auth / Clerk / NextAuth]
  • Styling: [Tailwind / CSS Modules]
  • Deployment: [Vercel / Railway / Fly.io]
  • Icons: [Lucide / Heroicons]

Frontend

  • Run /impeccable audit and /impeccable polish before shipping any UI. (Requires the impeccable plugin — remove this line if not installed.)
  • No inline styles. Use your CSS framework of choice.

Coding Rules

  • Keep files modular.
  • Keep files under 800 lines. At 800+, flag it and propose a split by responsibility (e.g. utils, hooks, sub-components) before adding more code. Never exceed 1,000 lines.
  • Never introduce breaking changes without explaining why.
  • No external libraries unless nothing installed works.
  • Use the project dependency file for correct versions. Never assume latest.
  • Keep a .env.example with every required var (names only, no values). Add, edit, or remove vars there whenever code changes require it, no need to ask each time. Never commit .env. If a project's .gitignore has a blanket .env* rule, add !.env.example so the template itself isn't excluded.
  • Comments: one line only. Explain why, not what. Example: // retry here because Stripe webhooks fire twice on timeout
  • Markdown files: kebab-case names (e.g. my-notes.md). Conventional root and meta docs keep their established uppercase names: README.md, CHANGELOG.md, CLAUDE.md, LICENSE, and the project memory files (PROJECT.md, MISTAKES.md, CONTRACT.md, REQUIREMENTS.md).
  • Watch for obvious bugs proactively.
  • When sweeping for a pattern, enumerate the full set present and diff against the allowed set. Don't grep only for instances already suspected.

Read the full file on GitHub · 164 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. 3d ago First seen · 164 lines · 2,252 tokens per session scan A 7097e415dbf1

Subscribe to this mod's changes

basecamp CLAUDE.md is an instructions file published in the GitHub repository janmaaarc/basecamp (7 stars, last pushed 23d ago), licensed MIT. It adds 2,252 tokens to every session, about $0.0113 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-31.