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/tanbamboo/awesome-claude-code-tips/claude-mdgit clone --depth 1 https://github.com/tanbamboo/awesome-claude-code-tipsWrote 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/tanbamboo/awesome-claude-code-tips/claude-md)<a href="https://agentmods.dev/instructions/tanbamboo/awesome-claude-code-tips/claude-md"><img src="https://agentmods.dev/badge/instructions/tanbamboo/awesome-claude-code-tips/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.00376 | $0.00376 |
| Opus 5 | $0.00188 | $0.00188 |
| Sonnet 5 | $0.00075 | $0.00075 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
awesome-claude-code-tips 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 5d 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.
What it actually says
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
This is a documentation repository called "awesome-claude-code-tips" containing comprehensive guidance for effective Claude Code usage. The repository contains:
README.md- Complete guide to Claude Code tips, session management, and workflowsexample-workflow.md- Detailed end-to-end example of git/GitHub workflows with Claude CodeCLAUDE.md- Project-specific guidance for this repository
Repository Purpose
This repository serves as a knowledge base and reference for developers using Claude Code. It's not a code project but rather a collection of best practices, workflows, and tips for effective AI-assisted development.
Git Workflow
Before implementing new features or functionality, create a new feature branch following the global instructions in ~/.claude/CLAUDE.md.
Project Structure
The repository structure will need to be established based on the chosen technology stack and project requirements.
Claude Code Session Management
Context Persistence:
- CLAUDE.md is automatically read at session start
- Project files persist between sessions
- Conversation history is cleared when session ends
- Each session starts fresh with file-based context
Updating CLAUDE.md:
- Ask to "update CLAUDE.md" during conversation to capture new context
- Include new build commands, architecture decisions, or project setup
- Best practice: update before ending session to preserve context for next time
- Keep focused on project-specific information, avoid generic advice
Session Lifecycle:
- Start: Reads CLAUDE.md and project files
- Active: Maintains conversation memory and file access
- End: Clears conversation memory, keeps files intact
- Next session: Starts fresh with updated CLAUDE.md context
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.
- 5d ago First seen · 43 lines · 376 tokens per session scan A c714d5b9ab64
awesome-claude-code-tips CLAUDE.md is an instructions file published in the GitHub repository tanbamboo/awesome-claude-code-tips (2 stars, last pushed 1y ago), licensed CC0-1.0. It adds 376 tokens to every session, about $0.0019 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.
Other instructions, from other repositories
crystal CLAUDE.md
Instructions for stravu/crystal, covering crystal - multi-session claude code manager, project overview, references, implementation status: ✅ complete and ✅ implemented features.
easy-cheese python.instructions.md
Instructions for paulnsorensen/easy-cheese, covering hard rules, what to flag and what not to flag.
plan-forge database.instructions.md
Database patterns for .NET — Dapper/EF Core, parameterized queries, migration strategy.
plan-forge naming.instructions.md
Azure naming conventions — Microsoft CAF abbreviations, constraints, uniqueness, tagging.
claude-bridge AGENTS.md
Instructions for kadaba/claude-bridge, covering agents.md — using claude-bridge from any ai coding cli, two independent channels, 1. coordination (the conversation), 2. file transfer (the bytes) — same for every tool and workflows.
AmbyKit CLAUDE.md
Claude Code instructions for ambystechcom/AmbyKit, covering claude code — notes for the ambykit repo and claude-specific.