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/lukefrankio/lukescopilotinstructions/google-testgit clone --depth 1 https://github.com/LukeFrankio/LukesCopilotInstructionsWrote 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/lukefrankio/lukescopilotinstructions/google-test)<a href="https://agentmods.dev/instructions/lukefrankio/lukescopilotinstructions/google-test"><img src="https://agentmods.dev/badge/instructions/lukefrankio/lukescopilotinstructions/google-test.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.08297 | $0.08297 |
| Opus 5 | $0.04149 | $0.04149 |
| Sonnet 5 | $0.01659 | $0.01659 |
| Haiku 4.5 | $0.00830 | $0.00830 |
Grade A, and why
LukesCopilotInstructions google-test.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 4d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 4d ago First seen · 842 lines · 8,297 tokens per session scan A 9ca46077f2e6
LukesCopilotInstructions google-test.instructions.md is an instructions file published in the GitHub repository LukeFrankio/LukesCopilotInstructions (1 stars, last pushed 3mo ago), with no licence file. It adds 8,297 tokens to every session, about $0.0415 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
presidio recognizers.instructions.md
Instructions for data-privacy-stack/presidio, covering recognizer changes, the load-bearing rule: test the configuration path, placement and naming, pattern scores and context words.
Math-To-Manim tests.instructions.md
Guidelines for writing and maintaining tests in Math-To-Manim.
plan-forge testing.instructions.md
Testing rules for Plan Forge — vitest patterns, fake-timers vs tolerance, mocking conventions, and how to read test output without hallucinating failures. Auto-loads when editing test files.
specs-driven-development-spring-angular frontend-code.instructions.md
Frontend code guardrails for Angular implementation, testing, and accessibility.
ai-instructions spring-boot-test.instructions.md
Spring Boot testing contract for layer-focused tests, API-contract assertions, and cross-cutting governance checks.
pr-narrator-mcp testing.instructions.md
Instructions for mhaviv/pr-narrator-mcp, covering test file review rules, mock setup (critical ordering), mock completeness, mock return values and test lifecycle.