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/whanyu1212/quantrl-lab/agents-mdgit clone --depth 1 https://github.com/whanyu1212/QuantRL-LabWrote 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/whanyu1212/quantrl-lab/agents-md)<a href="https://agentmods.dev/instructions/whanyu1212/quantrl-lab/agents-md"><img src="https://agentmods.dev/badge/instructions/whanyu1212/quantrl-lab/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.03951 | $0.03951 |
| Opus 5 | $0.01975 | $0.01975 |
| Sonnet 5 | $0.00790 | $0.00790 |
| Haiku 4.5 | $0.00395 | $0.00395 |
Grade A, and why
QuantRL-Lab AGENTS.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.
How it starts
The opening of the file, as written. The whole thing — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to agents (i.e., ADAL) when working with code in this repository.
Essential Commands
Package Management
This project uses uv (not Poetry). The lock file is uv.lock.
uv sync # Core deps only
uv sync --extra dev --extra notebooks # With dev/notebook extras
uv sync --all-extras # All optional features
source .venv/bin/activate
Optional dependency groups: dev, notebooks, ml (torch/transformers/litellm), tuning, viz, storage, full.
Testing
uv run pytest -m "not integration" # Unit tests only (CI/CD - no API keys needed)
uv run pytest -m integration # Integration tests (requires .env with API keys)
uv run pytest tests/data/test_indicators.py # Specific test file
uv run pytest -k "test_portfolio" # Tests matching pattern
uv run pytest --cov=quantrl_lab # With coverage
Code Quality (Pre-commit Hooks)
Pre-commit hooks run automatically on git commit. Run manually with:
pre-commit install # One-time setup
pre-commit run --all-files
pre-commit run --files path/to/file.py # Before committing changes
Hook configuration (.pre-commit-config.yaml):
- Black:
--line-length=120 --skip-string-normalization - isort:
--profile black - flake8:
--max-line-length=120 - docformatter: Google-style,
--wrap-summaries=72
CRITICAL: Always verify pre-commit hooks pass after making changes. Common failures: unused imports (flake8), line length violations, missing/malformed docstrings.
Documentation
uv run mkdocs serve # Local preview
uv run mkdocs build # Build (always run before committing API changes)
When renaming modules or changing public APIs, update docs/api-reference/ to match actual module paths and run mkdocs build to verify.
Standalone guide tabs (top-level nav, each a self-contained reference):
docs/DATA_SOURCES.md— data loaders, capability matrix, usage per sourcedocs/data-processing.md—DataProcessorandDataPipelinewith all 7 pipeline stepsdocs/environments.md— action/observation/reward spaces, all reward strategies, full env exampledocs/experiments.md—BacktestRunner,ExperimentJob,JobGenerator,AgentExplainer,OptunaRunner
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 · 372 lines · 3,951 tokens per session scan A 2614ee489158
QuantRL-Lab AGENTS.md is an instructions file published in the GitHub repository whanyu1212/QuantRL-Lab (53 stars, last pushed 4mo ago), licensed MIT. It adds 3,951 tokens to every session, about $0.0198 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-30.
Other instructions, from other repositories
kite-mcp-server CLAUDE.md
Claude Code instructions for Sundeepg98/kite-mcp-server, covering claude.md - kite mcp server, what it is, branch / repo, commands and deploy the hosted app (manual).
transformers copilot-instructions.md
Instructions for huggingface/transformers, covering copilot-instructions.md guide for hugging face transformers, core project structure, coding conventions for hugging face transformers, copying and inheritance and testing.
AReaL AGENTS.md
AGENTS.md instructions for areal-project/AReaL, covering agents.md -- areal agent operations guide, quick reference, environment, tests and cli docs.
Vibe-Research AGENTS.md
AGENTS.md instructions for simonlin1212/Vibe-Research, covering vibe-research-agent 金融研究宪法, 0. 三条不可越线, 1. 数据纪律(五问 gate:给出任何数字或结论前逐条自问), 2. 研究哲学(评估框架,不是预测工具) and 3. 估值口径(你只选输入、解释输出;计算交给 calc/).
Kokoro-FastAPI AGENTS.md
AGENTS.md instructions for remsky/Kokoro-FastAPI, covering agents.md, layout, commands, conventions and gotchas.
baba-is-auto AGENTS.md
AGENTS.md instructions for utilForever/baba-is-auto, covering agents.md, what this repository is, golden rules (read before any change), the most common task: changing simulator behavior and repository map.