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/jessinra/lorekeeper/testsgit clone --depth 1 https://github.com/Jessinra/LorekeeperWhat 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.00196 | $0.00196 |
| Opus 5 | $0.00098 | $0.00098 |
| Sonnet 5 | $0.00039 | $0.00039 |
| Haiku 4.5 | $0.00020 | $0.00020 |
Grade A, and why
Lorekeeper tests.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
Test Guidelines
Scope
Apply these rules to test code in tests/.
Review focus
- Tests should be deterministic and easy to diagnose when they fail.
- Prefer one behavior per test unless the grouping is very intentional.
- Cover edge cases, failure paths, and regressions — not just happy paths.
- Keep assertions specific enough to catch real regressions.
Repo conventions
- Match the project’s current pytest style and fixture patterns.
- When production code changes behavior, add or update tests in the same area.
- If a test depends on time, randomness, or order, freeze or control it explicitly.
- If a bug was fixed, add a regression test that would have caught it.
Review style
- Prefer clear test names that explain the behavior under test.
- Avoid overly broad fixtures or hidden setup that makes tests brittle.
- Keep test helpers small and local unless they are reused widely.
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 · 30 lines · 196 tokens per session scan A cc996511e497
Lorekeeper tests.instructions.md is an instructions file published in the GitHub repository Jessinra/Lorekeeper (4 stars, last pushed 29d ago), licensed Apache-2.0. It adds 196 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
hindsight CLAUDE.md
Instructions for vectorize-io/hindsight, covering claude.md, project overview, development commands, local development (api + ui) and start both api server and control plane ui.
m_flow AGENTS.md
AGENTS.md instructions for FlowElement-xinliuyuansu/m_flow, covering m-flow — developer & agent reference, 1. repository map, extension points, 2. local development and python backend (requires python 3.10 – 3.13).
plur CLAUDE.md
Instructions for plur-ai/plur, covering claude.md, what is plur, development, package dependency and version bumps.
dense-mem AGENTS.md
Instructions for markhuangai/dense-mem, covering dense-mem repository guidance, project context, architecture decision records, current stack and target architecture.
Meterless AGENTS.md
Instructions for Meterless/Meterless, covering agent instructions for meterless, routing table, isolation rule, repo-wide rules and non-coding agents.
open-bridge AGENTS.md
Instructions for bks-lab/open-bridge, covering the bridge — agent instructions, required reading, session start detection (automatic), theme and agents.