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.
npx agentmods add instructions/benkapner/claude-code-basecamp/claude-mdgit clone --depth 1 https://github.com/Benkapner/claude-code-basecampWrote 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/benkapner/claude-code-basecamp/claude-md)<a href="https://agentmods.dev/instructions/benkapner/claude-code-basecamp/claude-md"><img src="https://agentmods.dev/badge/instructions/benkapner/claude-code-basecamp/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 | $0.02176 | $0.02176 |
| Opus 5 | $0.01088 | $0.01088 |
| Sonnet 5 | $0.00435 | $0.00435 |
| Haiku 4.5 | $0.00218 | $0.00218 |
Grade A, and why
claude-code-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.
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
This is a meta-repository for Claude Code. It serves as a unified workspace with shared skills, commands, and hooks — so every team member gets consistent, high-quality AI assistance from day one.
Note: The "Agent Docs" listing below is auto-generated from frontmatter in markdown files in agent-docs/.
Critical Requirements
-
Read relevant documentation first - Before taking action on any task:
- Review the Agent Docs list below
- Read ALL documents relevant to your task before proceeding
- Re-evaluate after encountering failures or gaining new insights—additional documents may become relevant
-
Use
uvfor Python execution - Execute all scripts and tools withuv run <script/tool>. This workspace exclusively usesuvfor package and environment management. For scripts with inline dependencies (PEP 723), run them directly (uv run script.py) to ensure dependencies resolve correctly. -
Use available skills - Check if relevant skills are available in your environment for your tasks, and if there are - utilize them.
-
Verify before diagnosing - When analyzing failures or investigating issues, use documentation and available tools to verify facts. Provide diagnoses ONLY after verification.
-
Write minimal, correct code (Ponytail ladder) - Before writing any code, stop at the first rung that holds:
- Does this need to be built at all? (YAGNI)
- Does it already exist in this codebase? Reuse the helper, util, or pattern that's already here, don't re-write it.
- Does the standard library already do this? Use it.
- Does a native platform feature cover it? Use it.
- Does an already-installed dependency solve it? Use it.
- Can this be one line? Make it one line.
- Only then: write the minimum code that works.
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.
- 3d ago First seen · 178 lines · 2,176 tokens per session scan A e4f3f845fab0
claude-code-basecamp CLAUDE.md is an instructions file published in the GitHub repository Benkapner/claude-code-basecamp (16 stars, last pushed 14d ago), licensed MIT. It adds 2,176 tokens to every session, about $0.0109 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
personal-corp-os AGENTS.md
Instructions for serejaris/personal-corp-os, covering personal-corp-os, critical rules, never, structure and skill structure.
personal-corp-os CLAUDE.md
Instructions for serejaris/personal-corp-os, a project described as: Personal Corp OS — управление личной компанией через AI-агентов: задачи вне головы, отделы вместо памяти, недельное ретро. Открытые скиллы для Claude Code и Codex.
cortex-mem AGENTS.md
Instructions for sopaco/cortex-mem, covering cortex memory - ai agent context guide, project overview, core concepts, memory dimensions and three-tier layers.
vvvv-skills CLAUDE.md
Claude Code instructions for tebjan/vvvv-skills, covering vvvv gamma, when to patch vs code, core concepts, live environment and important conventions.
source-faithful-summary-skill AGENTS.md
Instructions for Kinneyzhang/source-faithful-summary-skill, covering agents.md — source-faithful summary skill, core behavior, optimization target, practical/workflow material and rules.
chealth CLAUDE.md
Instructions for danielithomas/chealth, covering claude.md, project purpose, language & tooling, build & test and architecture.