PerfGraph: Instructions file for Codex

AGENTS.md

PerfGraph AGENTS.md is an instructions file for Codex, OpenCode from Be1zebub/PerfGraph. It costs 1,070 tokens per session, scanned A, original, MIT.

An instruction file for PerfGraph, a command-line tool that measures real browser performance and produces a structured report. It explains how coding agents should run it and read its results.

In plain words
What is it for?
It helps analyze a website URL, collect browser data, inspect performance issues and causal chains, and use PerfGraph through its command line or MCP server.
Why use it?
It gives agents a defined process for turning browser measurements into identified problems, causes, and prioritized fixes.

Instructions file for CodexOpenCode

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

This is Be1zebub/PerfGraph's own configuration. It tells Codex and OpenCode how to work on PerfGraph 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 PerfGraph configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Be1zebub/PerfGraph. 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/Be1zebub/PerfGraph/master/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/Be1zebub/PerfGraph

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 PerfGraph AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/be1zebub/perfgraph/agents-md"><img src="https://agentmods.dev/badge/instructions/be1zebub/perfgraph/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,070 This file is loaded in full into every session.
When invoked 1,070 The same file — it is already loaded in full.
Security scan A 0 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.01070 $0.01070
Opus 5.5 $0.00428 $0.00428
Sonnet 5.5 $0.00214 $0.00214
Haiku 4.5 $0.00107 $0.00107

Measured 4d ago against content hash ee6d5558d3d2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

AGENTS.md · 112 lines

How it starts

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

PerfGraph — AI Agent Instructions

This file tells AI coding agents (Claude, ChatGPT, Copilot, etc.) how to work with PerfGraph.

What PerfGraph is

A CLI tool that collects real browser performance data via CDP, runs it through a 5-stage pipeline, and produces a structured report (TOON for agents, Markdown for humans) with causal chains and prioritized fixes. Designed to be consumed by AI agents.

collect → normalize → extract → analyze → report

How AI agents should use PerfGraph

Quick entry point

npx perfgraph run --url https://example.com --pretty

This runs the full pipeline. The output directory contains:

  • insights.toon — compact triage, metrics, warnings, and top recommendations
  • report.toon — issues, evidence, causal chains, and prioritized remediation
  • report.md — human-readable report
  • manifest.toon — artifact index and read order

summary.score is good / moderate / poor and lives inside insights.toon and report.toon.

The CLI needs Playwright's Chromium build. If it is missing, install it once with npx playwright install chromium — the CLI reports the expected binary path instead of a cryptic launch error.

AI agent workflow

For a URL plus performance, speed, loading, Core Web Vitals, Lighthouse, bottleneck, degradation, or causal-graph request, run:

perfgraph run --url <url> --output ./perfgraph-output --pretty

Read manifest.toon, then insights.toon, then report.toon. Read graph.toon and raw trace.json, network.json, or lighthouse.json only for targeted deep dives. .toon files are text, not JSON.

insights.toon holds two metric blocks: metrics from the PerfGraph run and lighthouse from Lighthouse's own navigation. They are different runs — cite each value with its source and never merge them.

The response should contain a short status, the 1–3 main causal chains as an ASCII graph, 3–5 prioritized actions, evidence/confidence, warnings, and a repeat-measurement plan. Do not treat Possible INP delay as measured INP or analyze a failed collection as a slow page. See skills/perfgraph/SKILL.md for the complete interpretation workflow.

Read the full file on GitHub · 112 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. 4d ago Changed · +13 lines · +155 tokens per session ee6d5558d3d2
  2. 1mo ago First seen · 99 lines · 915 tokens per session scan A 311d6855d470

Subscribe to this mod's changes

PerfGraph AGENTS.md is an instructions file published in the GitHub repository Be1zebub/PerfGraph (13 stars, last pushed 4d ago), licensed MIT. It adds 1,070 tokens to every session, about $0.0043 per session on Opus 5.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.

Related

Other instructions, from other repositories

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

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,581 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens