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/pascalporedda/awesome-claude-code/claude-mdgit clone --depth 1 https://github.com/pascalporedda/awesome-claude-codeWhat 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.01041 | $0.01041 |
| Opus 5 | $0.00521 | $0.00521 |
| Sonnet 5 | $0.00208 | $0.00208 |
| Haiku 4.5 | $0.00104 | $0.00104 |
Grade A, and why
awesome-claude-code 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 — 108 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
This is a Claude Code hooks project that implements sound notifications for various Claude Code events. The hooks are written in TypeScript and use native system commands to play sounds, requiring no external dependencies.
Development Commands
Since this project uses TypeScript hooks with no build step required:
- Test hooks locally:
npx tsx .claude/hooks/notification.ts --notify - No installation needed - hooks run directly via
npx tsx - Alternative runners:
pnpm dlx tsx,bunx tsx, orbun
Architecture & Key Components
Implemented Hooks
The project contains three TypeScript hooks in .claude/hooks/:
-
notification.ts - Plays notification sound when Claude needs user attention
- Triggered on Notification events
- Only plays sound with
--notifyflag - macOS: Uses built-in system sound
/System/Library/Sounds/Funk.aiff - Windows/Linux: Requires
on-agent-need-attention.wavin repository root - Alternative: Use
--speakflag on macOS to use voice synthesis instead (says "Your agent needs attention") - Logs events to
logs/notifications.json
-
stop.ts - Plays completion sound when Claude completes a task
- Triggered on Stop events
- Processes chat transcripts with
--chatflag - macOS: Uses built-in system sound
/System/Library/Sounds/Glass.aiff - Windows/Linux: Requires
on-agent-complete.wavin repository root - Alternative: Use
--speakflag on macOS to use voice synthesis instead (says "Your agent has finished") - Logs events to
logs/stop.jsonand transcripts tologs/chat.json
-
subagent_stop.ts - Plays completion sound when a subagent completes
- Triggered on SubagentStop events
- macOS: Uses built-in system sound
/System/Library/Sounds/Glass.aiff - Windows/Linux: Requires
on-agent-complete.wavin repository root - Alternative: Use
--speakflag on macOS to use voice synthesis instead (says "Your subagent has finished") - Logs events to
logs/subagent_stop.json
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 · 108 lines · 1,041 tokens per session scan A 5e1a4091b85d
awesome-claude-code CLAUDE.md is an instructions file published in the GitHub repository pascalporedda/awesome-claude-code (85 stars, last pushed 1y ago), licensed MIT. It adds 1,041 tokens to every session, about $0.0052 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
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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.