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/burakdede/lorepack/copilot-instructionsgit clone --depth 1 https://github.com/burakdede/lorepackWhat 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.00085 | $0.00085 |
| Opus 5 | $0.00043 | $0.00043 |
| Sonnet 5 | $0.00017 | $0.00017 |
| Haiku 4.5 | $0.00009 | $0.00009 |
Grade A, and why
lorepack copilot-instructions.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 2d 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
The project rules for this repository live in AGENTS.md.
Read it before starting any work. It covers the design direction and non-negotiable invariants, the requirement that all work be tracked as a backlog task first, commit and PR conventions (including: never author commits, no AI attribution), the testing bar, documentation expectations, and how to choose an implementation and its dependencies.
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.
- 2d ago First seen · 7 lines · 85 tokens per session scan A a59b6fa04303
lorepack copilot-instructions.md is an instructions file published in the GitHub repository burakdede/lorepack (2 stars, last pushed 12d ago), licensed Apache-2.0. It adds 85 tokens to every session, about $0.0004 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
cloudflare-workers-nextjs-saas-template AGENTS.md
Instructions for LubomirGeorgiev/cloudflare-workers-nextjs-saas-template, covering project context, vinext, general coding rules, control flow and comments.
zuke AGENTS.md
Instructions for zuke-build/zuke, covering agents.md, using zuke — the api, without guessing, tech stack, typescript 7 / tsgo and coding guidelines (non-negotiable).
flarestarter CLAUDE.md
Instructions for FlareStarter/flarestarter: This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
baerly-storage CLAUDE.md
Toolchain, verification matrix, module map, conventions, anti-patterns. The main agent entry point.
munkel CLAUDE.md
Instructions for limehq/munkel, covering claude.md, monorepo layout, commands, macos development specifics and deploy.
ai-coding-primer CLAUDE.md
Instructions for ammonhaggerty/ai-coding-primer, covering claude.md, repository structure, guidebook chapters, constraints and writing tone.