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/avibebuilder/claude-prime/claude-mdgit clone --depth 1 https://github.com/avibebuilder/claude-primeWrote 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/avibebuilder/claude-prime/claude-md)<a href="https://agentmods.dev/instructions/avibebuilder/claude-prime/claude-md"><img src="https://agentmods.dev/badge/instructions/avibebuilder/claude-prime/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.01222 | $0.01222 |
| Opus 5 | $0.00611 | $0.00611 |
| Sonnet 5 | $0.00244 | $0.00244 |
| Haiku 4.5 | $0.00122 | $0.00122 |
Grade A, and why
claude-prime 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.
How it starts
The opening of the file, as written. The whole thing — 99 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 when working with this repository.
Project overview
A boilerplate toolkit that supercharges Claude Code with skills, commands, and workflows for agent-skill-driven development.
Context engineering philosophy
Context engineering is about curating the optimal set of tokens to maximize desired model behavior. Unlike prompt engineering (crafting perfect prompts), context engineering considers the holistic state available to the LLM at any moment.
Core Principles
1. Context is a Finite Resource
Models have limited attention budgets that degrade as context grows (context rot). Goal: find the smallest high-signal set of tokens that maximizes desired outcomes. Every token competes for attention.
2. Right-Altitude Prompting
Concrete but not hardcoded. Find the Goldilocks zone.
| Too Low (Brittle) | Too Vague | Right Altitude |
|---|---|---|
| "Use Tailwind's blue-500" | "Make it look good" | "Use project's existing color system" |
| "Set font-size to 16px" | "Use appropriate sizing" | "Match surrounding components" |
3. Avoid Railroading Claude
Claude will generally try to stick to your instructions, and because Skills are so reusable you’ll want to be careful of being too specific in your instructions. Give Claude the information it needs, but give it the flexibility to adapt to the situation
4. Don’t State the Obvious
Claude Code knows a lot about your codebase, and Claude knows a lot about coding, including many default opinions. If you’re publishing a skill that is primarily about knowledge, try to focus on information that pushes Claude out of its normal way of thinking.
5. Anti-Convergence Patterns
LLMs default to high-probability outputs. Counter by listing what to avoid, suggesting uncommon alternatives, varying examples, and breaking monotony.
6. Just-in-Time Context Retrieval
Don't load everything upfront. Maintain lightweight identifiers (file paths, URLs) and retrieve dynamically at runtime.
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 · 99 lines · 1,222 tokens per session scan A 2f46bc1c0fbe
claude-prime CLAUDE.md is an instructions file published in the GitHub repository avibebuilder/claude-prime (119 stars, last pushed 3mo ago), licensed MIT. It adds 1,222 tokens to every session, about $0.0061 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
mex CLAUDE.md
Claude Code instructions for mex-memory/mex, a project described as: Persistent project memory for AI coding agents. Structured scaffold + drift detection CLI.
mex AGENTS.md
AGENTS.md instructions for mex-memory/mex, a project described as: Persistent project memory for AI coding agents. Structured scaffold + drift detection CLI.
ham CLAUDE.md
Instructions for kromahlusenii-ops/ham, covering ham — hierarchical agent memory skill, what this is, key files, rules and agent memory system.
claude-beads CLAUDE.md
Instructions for voxpelli/claude-beads, covering claude.md, what this is, plugin layout, components and agent (1).
ai-memory CLAUDE.md
Claude Code instructions for blockmandev/ai-memory, covering project memory instructions, when to save memories (addmemory), memory types, importance levels and when to search memories (searchmemories).
mcp-structured-memory CLAUDE.md
Claude Code instructions for nmeierpolys/mcp-structured-memory, a project described as: Structured Memory MCP Server.