Borrowing it
Nothing to install: this file belongs to hogeheer499-commits/strix-halo-guide. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hogeheer499-commits/strix-halo-guide/main/AGENTS.mdgit clone --depth 1 https://github.com/hogeheer499-commits/strix-halo-guideWrote 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/hogeheer499-commits/strix-halo-guide/agents-md)<a href="https://agentmods.dev/instructions/hogeheer499-commits/strix-halo-guide/agents-md"><img src="https://agentmods.dev/badge/instructions/hogeheer499-commits/strix-halo-guide/agents-md/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.
<a href="https://agentmods.dev/instructions/hogeheer499-commits/strix-halo-guide/agents-md"><img src="https://agentmods.dev/badge/instructions/hogeheer499-commits/strix-halo-guide/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.02053 | $0.02053 |
| Opus 5 | $0.01026 | $0.01026 |
| Sonnet 5 | $0.00411 | $0.00411 |
| Haiku 4.5 | $0.00205 | $0.00205 |
Grade A, and why
strix-halo-guide 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 11d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Operational instructions for Codex agents working in this repository.
Core Project Lens
strix-halo-guide is primarily an evidence-backed AMD Strix Halo / Ryzen AI MAX+ 395 local-AI setup and benchmark guide.
The project now also has a vendor / partner / sponsor-facing direction: benchmark work should show how the guide reduces adoption friction for AMD Strix Halo / Ryzen AI MAX+ local-AI hardware.
When the user asks "is er nieuws?", "updates?", "wat moeten we testen?", or anything similar, evaluate updates through two layers:
-
Technical value:
- new models
- new
llama.cpp, Ollama, ROCm, Mesa, vLLM, driver, BIOS, or tooling changes - benchmark regressions or improvements
- new blockers, fixes, or reproducibility risks
-
Adoption / commercial value:
- what buyer uncertainty does this remove?
- what setup friction does this reduce?
- what vendor/OEM/reviewer/product question does this answer?
- what evidence would make someone more confident buying, recommending, supporting, or reviewing the hardware?
- what missing hardware, firmware, driver support, vendor contact, or community data is needed to prove the next thing?
Higher t/s is useful, but it is not the only priority. Treat benchmarks as the proof layer and vendor/partner/sponsor docs as the leverage layer.
Documentation Style
- Write in clear, professional English.
- Keep the repo primarily useful to developers, buyers, and benchmark contributors.
- Keep vendor-facing language credible, independent, and evidence-based.
- Prefer links to existing evidence over duplicating long benchmark sections.
- Use TODO placeholders for missing stats, contact details, quotes, traffic, sponsors, or evidence.
- Preserve negative results, caveats, and failed paths.
- Do not make the README feel like an advertisement.
- Keep machine-specific workflow, local services, ports, account operations, and private maintainer procedures out of public docs.
Do-Not-Invent Rules
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.
- 11d ago First seen · 147 lines · 2,053 tokens per session scan A 8ddb30b78a8a
strix-halo-guide AGENTS.md is an instructions file published in the GitHub repository hogeheer499-commits/strix-halo-guide (325 stars, last pushed 2d ago), licensed MIT. It adds 2,053 tokens to every session, about $0.0103 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
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.
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.
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).
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.