Lorekeeper: Instructions file for GitHub Copilot

.github/instructions/tests.instructions.md

Lorekeeper tests.instructions.md is an instructions file for GitHub Copilot from Jessinra/Lorekeeper. It costs 196 tokens per session, scanned A, original, Apache-2.0.

A set of rules for writing and reviewing tests with pytest, a tool for running Python tests.

In plain words
What is it for?
Use it when adding or changing tests, fixing a bug, controlling time or randomness in tests, or reviewing test code.
Why use it?
It helps tests fail for clear reasons and catch edge cases, error paths, and regressions rather than only confirming the normal case.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is Jessinra/Lorekeeper's own configuration. It tells GitHub Copilot how to work on Lorekeeper itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Lorekeeper configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Jessinra/Lorekeeper. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Jessinra/Lorekeeper/main/.github/instructions/tests.instructions.md
Clone the repo
git clone --depth 1 https://github.com/Jessinra/Lorekeeper

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for Lorekeeper tests.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/jessinra/lorekeeper/tests/github.svg)](https://agentmods.dev/instructions/jessinra/lorekeeper/tests)
Your own site
<a href="https://agentmods.dev/instructions/jessinra/lorekeeper/tests"><img src="https://agentmods.dev/badge/instructions/jessinra/lorekeeper/tests/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.

agentmods 80×15 button for Lorekeeper tests.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/jessinra/lorekeeper/tests"><img src="https://agentmods.dev/badge/instructions/jessinra/lorekeeper/tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 196 This file is loaded in full into every session.
When invoked 196 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00196 $0.00196
Opus 5.5 $0.00078 $0.00078
Sonnet 5.5 $0.00039 $0.00039
Haiku 4.5 $0.00020 $0.00020

Measured 1mo ago against content hash cc996511e497, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

.github/instructions/tests.instructions.md · 30 lines

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.
Changes

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.

  1. 1mo ago First seen · 30 lines · 196 tokens per session scan A cc996511e497

Subscribe to this mod's changes

Lorekeeper tests.instructions.md is an instructions file published in the GitHub repository Jessinra/Lorekeeper (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 196 tokens to every session, about $0.0008 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.

Related

Other instructions, from other repositories