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/aeon-7/aeon-bench-pod/agents-mdgit clone --depth 1 https://github.com/AEON-7/Aeon-Bench-PodWrote 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/aeon-7/aeon-bench-pod/agents-md)<a href="https://agentmods.dev/instructions/aeon-7/aeon-bench-pod/agents-md"><img src="https://agentmods.dev/badge/instructions/aeon-7/aeon-bench-pod/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.32917 | $0.32917 |
| Opus 5 | $0.16459 | $0.16459 |
| Sonnet 5 | $0.06583 | $0.06583 |
| Haiku 4.5 | $0.03292 | $0.03292 |
Grade D, and why
Aeon-Bench-Pod AGENTS.md scanned grade D with 4 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 6d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
curl -s http://127.0.0.1:8000/v1/chat/completions -H 'Content-Type: application/json' -d '{ Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
docker info # 1. daemon reachable, and reachable WITHOUT sudo docker run --rm hello-world # 2. you can actually create containers Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
2. Append it to the serving host's `~/.ssh/authorized_keys`: Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Check: `curl -s localhost:8091/healthz`. How it starts
The opening of the file, as written. The whole thing — 1,914 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — AEON Bench Pod operating manual for AI agents
You (an AI agent) are here to deploy the AEON Bench Pod and run a COMPLETE, VALIDATED benchmark FOR a non-technical human, then hand them the results and a live link. This file is the whole manual. It is written so you need nothing else: copy-paste command blocks, the exact Run-tab flow, the engine/recipe reference, and the trust rules that decide whether a run ranks.
Two roles ship in one image: the pod (a local benchmark appliance on the human's own hardware) and the mothership (the public leaderboard at aeon-bench.com). This manual is the pod-operator role. The judge / run-loop contract that used to live here is preserved verbatim in the Appendix at the bottom.
Humans who want screenshots: point them at
docs/walkthrough/README.md(illustrated walkthrough). The copy-paste TL;DR for humans isdocs/pod-quickstart.md; the narrative guide isdocs/run-a-benchmark.md.
THE SHORT VERSION — this is the whole job
If you read nothing else, do this. Four steps. Everything after this section is reference you only need when something is unusual or breaks.
1. Start the pod. Pull first, every session.
docker pull ghcr.io/aeon-7/aeon-pod:latest && docker rm -f aeon-pod
docker run -d --name aeon-pod --network host --gpus all \
-v /var/run/docker.sock:/var/run/docker.sock -v aeon-pod-state:/root/.aeon \
-v "$HOME/aeon-models:/models" -e AEON_MODELS_HOST_DIR="$HOME/aeon-models" \
-v "$HOME:/host-home:ro" -e AEON_HOST_HOME_DIR="$HOME" \
ghcr.io/aeon-7/aeon-pod:latest
No NVIDIA GPU? Drop --gpus all and swap --network host for -p 8091:8091.
Check: curl -s localhost:8091/healthz.
2. Point at the model. One question: is it already running as a server?
ALREADY RUNNING -> aeon_pod_scan_endpoints() # gives hf_guess + url
aeon_pod_run(hf_link=<hf_guess>, serve_url=<url>, verify_endpoint=true)
# on another machine, add remote_host="user@host" to BOTH
NOT RUNNING -> aeon_pod_run(hf_link="org/Model") # pod downloads + verifies
ON DISK ALREADY -> aeon_pod_scan_models() # gives repo id + path
aeon_pod_run(hf_link=<repo>, local_dir=<path>)
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.
- 6d ago First seen · 1,914 lines · 32,917 tokens per session scan D 7de3cd415a32
Aeon-Bench-Pod AGENTS.md is an instructions file published in the GitHub repository AEON-7/Aeon-Bench-Pod (25 stars, last pushed 20d ago), licensed MIT. It adds 32,917 tokens to every session, about $0.1646 per session on Opus 5. A static security scan graded it D with 4 findings (sends data to an external url, asks for root, reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
Qwen3.6-27B-AEON-Ultimate-Uncensored-DFlash AGENTS.md
Instructions for AEON-7/Qwen3.6-27B-AEON-Ultimate-Uncensored-DFlash, covering agents.md — operator's manual for ai agents, tl;dr for agents (60 seconds), do not undo — common stale-documentation traps, 1. don't force the marlin nvfp4 backend and 2. don't set enablenvfp4sm100=1.
agent-bench AGENTS.md
Instructions for cipherfoxie/agent-bench, covering agents, multi-agent contract for agent-bench, project ethos, rules and adding an experiment (the only common task).
mcp-llm-eval CLAUDE.md
Claude Code instructions for berkayildi/mcp-llm-eval, covering claude.md — mcp-llm-eval, project overview, directory structure, key design decisions and mcp tool signatures.
langwatch CLAUDE.md
Claude Code instructions for langwatch/langwatch, covering langwatch, before you implement anything, development environment, running with no container runtime and local dev by hostname — thuishaven / portless (recommended).
ClawBench AGENTS.md
AGENTS.md instructions for TIGER-AI-Lab/ClawBench, covering clawbench -- agent context, what this is, project structure, setup and 2. configure at least one model.
strix-halo-guide AGENTS.md
AGENTS.md instructions for hogeheer499-commits/strix-halo-guide, covering agents.md, core project lens, documentation style, do-not-invent rules and benchmark claim rules.