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/noambrown/poker_solver/agents-mdgit clone --depth 1 https://github.com/noambrown/poker_solverWrote 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/noambrown/poker_solver/agents-md)<a href="https://agentmods.dev/instructions/noambrown/poker_solver/agents-md"><img src="https://agentmods.dev/badge/instructions/noambrown/poker_solver/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.1 | $0.00646 | $0.00646 |
| Opus 5 | $0.00323 | $0.00323 |
| Sonnet 5 | $0.00129 | $0.00129 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
poker_solver 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 5d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Overview
This repo builds a no-limit Texas hold'em river subgame solver, starting with Kuhn and Leduc poker. Core algorithms include CFR, CFR+, external-sampling MCCFR, Fictitious Play (simul/alt), and FLOP. The Python implementation is the reference; the optimized C++ implementation lives in cpp/. Optimize only after matching Python results.
Project Structure & Module Organization
python/reference implementation withpython/src/algorithms/,python/src/games/,python/src/cli/, andpython/tests/.cpp/optimized river solver (performance-focused).docs/design notes and algorithm references (add if needed).configs/run configs (YAML/JSON) for reproducible experiments (add if needed).scripts/orexperiments/reproducible runs and benchmarks (add if needed).artifacts/generated results; keep large outputs out of git (add if needed).
Build, Test, and Development Commands
Standardize developer commands in a Makefile (add if missing) and keep targets stable:
make setup- install dependencies and tooling.make test- run the full test suite (all languages present).make lint- static checks.make fmt- formatting.make run LANG=python GAME=kuhn ALGO=cfr- local run for a given game/algorithm. Until aMakefileexists, use direct commands likepython -m pytest python/tests.
Coding Style & Naming Conventions
- Indentation: 4 spaces, no tabs; keep files ASCII.
- Names:
snake_casefor functions/modules,PascalCasefor types,UPPER_SNAKEfor constants. - Prefer pure functions and immutable data where practical; centralize RNG and logging.
- Tooling: Python uses
ruff(format/lint) andmypy(types); Rust usesrustfmtandclippy; C++ usesclang-formatandclang-tidyonce configured.
Testing Guidelines
- Framework:
pytestfor Python unit and convergence tests. - Naming:
python/tests/test_*.py; use deterministic seeds. - Add regression tests for exploitability thresholds on Kuhn/Leduc; ports must match these results.
- Coverage: keep algorithm modules at >=90%; justify any exclusions.
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.
- 5d ago First seen · 44 lines · 646 tokens per session scan A b25147eca261
poker_solver AGENTS.md is an instructions file published in the GitHub repository noambrown/poker_solver (165 stars, last pushed 8mo ago), licensed MIT. It adds 646 tokens to every session, about $0.0032 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
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).