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/barakgut/lore/claude-mdgit clone --depth 1 https://github.com/barakgut/loreWrote 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/barakgut/lore/claude-md)<a href="https://agentmods.dev/instructions/barakgut/lore/claude-md"><img src="https://agentmods.dev/badge/instructions/barakgut/lore/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.00202 | $0.00202 |
| Opus 5 | $0.00101 | $0.00101 |
| Sonnet 5 | $0.00040 | $0.00040 |
| Haiku 4.5 | $0.00020 | $0.00020 |
Grade A, and why
lore 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.
What it actually says
lore
Agent skills
Issue tracker
Issues live as local markdown files under .scratch/<feature-slug>/. See docs/agents/issue-tracker.md.
Triage labels
The five canonical triage roles use their default label strings (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix). See docs/agents/triage-labels.md.
Domain docs
Single-context: CONTEXT.md and docs/adr/ at the repo root, both created lazily. See docs/agents/domain.md.
Git commits
Write commit messages that end at their last content line: subject, optional body, nothing after. Attribution trailers (Co-Authored-By, Generated with) are omitted here — authorship is the committer's.
Keep the subject line at 100 characters or fewer, and the body (everything below it) at 200 characters or fewer.
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 · 22 lines · 202 tokens per session scan A 85b318d43a5c
lore CLAUDE.md is an instructions file published in the GitHub repository barakgut/lore (1 stars, last pushed 6d ago), licensed MIT. It adds 202 tokens to every session, about $0.0010 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
hplan CLAUDE.md
Instructions for kimsanguine/hplan, covering claude.md — hplan project rules (adk l1: memory), hplan context, 9 behavioral rules, rule 1 — think before coding and rule 2 — simplicity first.
octowiz CLAUDE.md
Instructions for raelli/octowiz, covering octowiz, releasing & deploying, commands, agent skills and issue tracker.
vibe-engineering AGENTS.md
Instructions for ash1794/vibe-engineering, covering vibe-engineering, skills, invocation, tool mapping and project conventions.
product-manager CLAUDE.md
Instructions for julianoczkowski/product-manager, covering claude.md, repo layout, skill conventions, how updates reach installed users (important) and releasing (tags + github releases).
forge CLAUDE.md
Instructions for zjio26/forge, covering claude.md, project overview, architecture, wave-based processing and test layering.
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).