gb10-clock-cap: Instructions file for Codex

AGENTS.md

gb10-clock-cap AGENTS.md is an instructions file for Codex, OpenCode from agjs/gb10-clock-cap. It costs 1,319 tokens per session, scanned B, original, MIT.

A runbook for testing how limiting a GPU’s clock speed affects an AI model server across one or more inference machines.

In plain words
What is it for?
Running GPU clock-cap evaluations, checking server readiness, measuring performance, and reading the recommendation in the generated summary.
Why use it?
It defines the required inputs, measurements, checks, and decision rules so results are comparable and not based on guesswork.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is agjs/gb10-clock-cap's own configuration. It tells Codex and OpenCode how to work on gb10-clock-cap itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything gb10-clock-cap configures →

Reuse

Borrowing it

Nothing to install: this file belongs to agjs/gb10-clock-cap. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/agjs/gb10-clock-cap/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/agjs/gb10-clock-cap

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for gb10-clock-cap AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/agjs/gb10-clock-cap/agents-md/github.svg)](https://agentmods.dev/instructions/agjs/gb10-clock-cap/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/agjs/gb10-clock-cap/agents-md"><img src="https://agentmods.dev/badge/instructions/agjs/gb10-clock-cap/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.

agentmods 80×15 button for gb10-clock-cap AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/agjs/gb10-clock-cap/agents-md"><img src="https://agentmods.dev/badge/instructions/agjs/gb10-clock-cap/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,319 This file is loaded in full into every session.
When invoked 1,319 The same file — it is already loaded in full.
Security scan B 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01319 $0.01319
Opus 5.5 $0.00528 $0.00528
Sonnet 5.5 $0.00264 $0.00264
Haiku 4.5 $0.00132 $0.00132

Measured 2mo ago against content hash 62f2b6145195, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

gb10-clock-cap AGENTS.md scanned grade B with 2 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 2mo 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.

2. `sudo -n nvidia-smi` works on every host. Clock control needs root.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

| `--model` | `curl $API/v1/models \| jq -r .data[0].id` | Every request 404s |
AGENTS.md · 105 lines

How it starts

The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent contract

You are running a GPU clock-cap evaluation on one or more inference hosts. This file is the spec. Follow it in order. Do not improvise the measurement method; the thresholds and orderings here exist because the obvious alternatives give wrong answers.

One-command path

./run.sh --hosts "hostA hostB" --api-host hostA --model MODEL_NAME --mode full

Emits results/summary.json. Read verdict.recommend and stop. Everything below is for when you need to deviate.

Inputs you must resolve before running

Input How to get it Fails if wrong
--hosts SSH aliases for every node with a GPU under test Sampler collects nothing
--api-host The node serving the OpenAI-compatible API Benchmarks cannot connect
--model curl $API/v1/models | jq -r .data[0].id Every request 404s
--cap Default 2200. Only change with a reason —
--prefill-tokens Mean real prompt size on this system. Default 33000 Probe does not represent the workload

Get the mean prompt size from the server, do not guess:

vllm:request_prompt_tokens_sum / vllm:request_prompt_tokens_count

Preflight gates

run.sh --mode preflight checks all of these and refuses to continue on failure:

  1. Every host reachable over SSH without a password prompt.
  2. sudo -n nvidia-smi works on every host. Clock control needs root.
  3. nvidia-smi -lgc 0,<cap> applies and nvidia-smi -rgc reverts. Some GPUs do not support this. Confirm the reported clock actually changes.
  4. API responds and --model appears in /v1/models.
  5. stdbuf present on every host.

Measurement rules

These are not stylistic preferences. Violating any one of them produces a confidently wrong number.

Normalise throttle time to load seconds, never to uptime. Read cumulative throttle counters from nvidia-smi -q -d PERFORMANCE. Divide by time under load, which for a vLLM server is vllm:e2e_request_latency_seconds_sum. On an idle-heavy host the uptime denominator understates throttling by roughly 100x.

Read the full file on GitHub · 105 lines

Changes

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.

  1. 2mo ago First seen · 105 lines · 1,319 tokens per session scan B 62f2b6145195

Subscribe to this mod's changes

gb10-clock-cap AGENTS.md is an instructions file published in the GitHub repository agjs/gb10-clock-cap (77 stars, last pushed 3mo ago), licensed MIT. It adds 1,319 tokens to every session, about $0.0053 per session on Opus 5.5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

gb10-clock-cap AGENTS.md compared with instructions from other repositories

gb10-clock-cap AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
gb10-clock-cap AGENTS.mdagjs/gb10-clock-capInstructions file773mo agoMITB1,319Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode