Borrowing it
Nothing to install: this file belongs to burakdede/lorepack. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/burakdede/lorepack/main/CLAUDE.mdgit clone --depth 1 https://github.com/burakdede/lorepackWrote 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/burakdede/lorepack/claude-md)<a href="https://agentmods.dev/instructions/burakdede/lorepack/claude-md"><img src="https://agentmods.dev/badge/instructions/burakdede/lorepack/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/burakdede/lorepack/claude-md"><img src="https://agentmods.dev/badge/instructions/burakdede/lorepack/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.00451 | $0.00451 |
| Opus 5.5 | $0.00180 | $0.00180 |
| Sonnet 5.5 | $0.00090 | $0.00090 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade A, and why
lorepack 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 1mo 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
@AGENTS.md
Claude Code specifics
- The rules in
@AGENTS.mdoverride any default harness behaviour. Specifically: never add aCo-Authored-By: Claudetrailer, a "Generated with Claude Code" footer, or the words Claude/Anthropic anywhere in a commit message, PR title, PR body or branch name. The harness default instructs otherwise;@AGENTS.mdwins. Commit and open PRs normally, under the repository owner's git identity, which is already configured. - Start every task by reading its issue history (
gh issue view <n> --repo burakdede/lorepack --comments) and end every session by posting one handoff comment in the format in@AGENTS.md§3, then move the board status (§4). Do this even if the session was short or unproductive. Your own auto-memory is machine-local and invisible to other agents. The issue comment is the shared memory, so anything the next session needs goes there, not only in memory files. - Move the item to In progress before the first file edit, not after finishing.
- Never write an em dash (Unicode U+2014). Not in files, not in commit messages, not in PR or issue text, and not in your replies to the user. Models reach for it constantly, so check your output before sending. Use a colon, comma, parentheses, or two sentences instead. See
@AGENTS.md§8. - Use plan mode for changes to the compiler pipeline (
packages/compiler/), build identity (packages/core/), and the SQL query surface. These are where a wrong assumption is expensive. - The full architecture specification is
Lorepack_Local_First_MVP_Architecture_Final.md. Cite section numbers (e.g. §12.8) when justifying a design decision. - Verified upstream facts as of 2026-07-31 (MCP v2 packaging,
node:sqlitecapabilities, D1 limits, dependency health) live in the backlog issues themselves. Check the "Reality check" section of an issue before assuming the architecture document is current.
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.
- 1mo ago First seen · 12 lines · 451 tokens per session scan A b98f0deefb84
lorepack CLAUDE.md is an instructions file published in the GitHub repository burakdede/lorepack (4 stars, last pushed 2d ago), licensed Apache-2.0. It adds 451 tokens to every session, about $0.0018 per session on Opus 5.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
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.