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/quintesse/leyden-perf-test/agents-mdgit clone --depth 1 https://github.com/quintesse/leyden-perf-testWrote 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/quintesse/leyden-perf-test/agents-md)<a href="https://agentmods.dev/instructions/quintesse/leyden-perf-test/agents-md"><img src="https://agentmods.dev/badge/instructions/quintesse/leyden-perf-test/agents-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.08606 | $0.08606 |
| Opus 5 | $0.04303 | $0.04303 |
| Sonnet 5 | $0.01721 | $0.01721 |
| Haiku 4.5 | $0.00861 | $0.00861 |
Grade B, and why
leyden-perf-test AGENTS.md scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
# Ubuntu/Debian: sudo apt-get install docker.io How it starts
The opening of the file, as written. The whole thing — 1,113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - Leyden Performance Test Harness
Project Overview
Purpose
This is a performance testing harness designed to evaluate JVM applications, with a primary focus on testing Project Leyden's Ahead-of-Time (AOT) compilation features. The harness enables systematic comparison of different JVM configurations, compilation strategies, and runtime behaviors across multiple Java versions.
Primary Goals
- Benchmark Leyden AOT Performance: Measure and compare the performance impact of Leyden's AOT compilation features
- Multi-Version Testing: Support testing across multiple JVM versions (currently targeting JDK 25, 26+)
- Reproducible Results: Provide consistent, reproducible performance measurements
- Extensibility: Enable easy addition of new test suites, drivers, and strategies
- Automation-Friendly: Design for both human operators and AI agents
Current State
- Status: Active development
- Maturity: Stable for internal performance testing
- Primary Use Case: Evaluating Leyden JVM features and comparing JVM performance characteristics
- Target Users: AI agents, performance engineers, JVM developers
Architecture
Core Components
leyden-perf-test/
├── run # Main entry point - bash launcher
├── src/
│ ├── scripts/
│ │ ├── bin/ # Command implementations (test.sh, list.sh, etc.)
│ │ ├── drivers/ # Test drivers (oha, ohac, hyperfoil)
│ │ ├── strategies/ # Test strategies (normal, aot)
│ │ ├── *funcs.sh # Shared function libraries
│ │ └── launcher.sh # Core orchestration logic
│ ├── java/util/ # Java analysis utilities (Collate, Graph, etc.)
│ └── qdup/ # qdup configuration (alternative test runner)
├── tests/ # Main test suites (production workloads)
├── tests-dummy/ # Dummy tests for harness validation
├── tests-template/ # Templates for creating new tests
├── profiles/ # Configuration profiles (lowmem, diagnostics, etc.)
├── verify/bats/ # Harness verification tests
├── test-results/ # Test output directory
└── cache/ # Build artifacts and 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.
- 4d ago First seen · 1,113 lines · 8,606 tokens per session scan B 1725413669d9
leyden-perf-test AGENTS.md is an instructions file published in the GitHub repository quintesse/leyden-perf-test (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 8,606 tokens to every session, about $0.0430 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
questdb CLAUDE.md
Claude Code instructions for questdb/questdb, covering claude.md, project overview, coding guidelines, tests and questdb's sql dialect.
liteflow CLAUDE.md
Instructions for dromara/liteflow, covering claude.md, 概述, 命令, 构建 and 构建整个项目（模块集由 jdk 版本自动选择 —— 见下方说明）.
BitcoinAddressFinder CLAUDE.md
Claude Code instructions for bernardladenthin/BitcoinAddressFinder, covering claude.md — bitcoinaddressfinder, project overview, build system, common commands and compile only.
imgui-java CLAUDE.md
Claude Code instructions for SpaiR/imgui-java: This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
langchain4j-cdi copilot-instructions.md
Copilot instructions for langchain4j/langchain4j-cdi, covering langchain4j cdi integration, working effectively, prerequisites, bootstrap and build and essential commands.
copilot-setting testing.instructions.md
Load when writing or reviewing a Test.java / IT.java file — JUnit 4 + Mockito + Spring Test 3.2. Triggers on: @RunWith(MockitoJUnitRunner / SpringJUnit4ClassRunner), org.junit.Test, @Before/@After, @Transactional auto-rollback. Not JUnit 5 (@BeforeEach/@ExtendWith) or @SpringBootTest. Defer non-test Java to…