What is codex-usage-heatmap AGENTS.md?

Project instructions for Codex Usage Heatmap, a local Node.js and TypeScript command-line program that turns Codex activity logs into daily heatmaps and reports.

Use them when changing this repository so the agent knows where parsing, aggregation, rendering, exports, tests, and command-line code belong, and which checks to run.

They give a coding agent the project layout, required commands, and rules for building, testing, linting, and checking changes.

How Gatsby007max/codex-usage-heatmap configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to Gatsby007max/codex-usage-heatmap. 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/Gatsby007max/codex-usage-heatmap/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/Gatsby007max/codex-usage-heatmap

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/gatsby007max/codex-usage-heatmap/agents-md/github.svg)](https://agentmods.dev/instructions/gatsby007max/codex-usage-heatmap/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/gatsby007max/codex-usage-heatmap/agents-md"><img src="https://agentmods.dev/badge/instructions/gatsby007max/codex-usage-heatmap/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/gatsby007max/codex-usage-heatmap/agents-md"><img src="https://agentmods.dev/badge/instructions/gatsby007max/codex-usage-heatmap/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 615 This file is loaded in full into every session.

When invoked 615 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.

Model	Per session	Once invoked
Fable 5.1	$0.00615	$0.00615
Opus 5.5	$0.00246	$0.00246
Sonnet 5.5	$0.00123	$0.00123
Haiku 4.5	$0.00061	$0.00061

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

Security

Grade A, and why

codex-usage-heatmap 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 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.

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 · 79 lines

How it starts

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

Codex Usage Heatmap Agent Guide

Project Overview

Codex Usage Heatmap is a local-only Node.js and TypeScript CLI that scans local Codex JSONL logs, extracts token usage metadata, aggregates usage by day, and renders a GitHub-style heatmap as JSON, CSV, SVG, and static HTML.

Repository Layout

src/cli.ts wires the command line interface.
src/commands/ contains command handlers.
src/core/ contains discovery, privacy, reading, normalization, aggregation, and date logic.
src/parsers/ contains parser adapters for unstable Codex log shapes.
src/render/ contains SVG and HTML report rendering.
src/exporters/ contains JSON and CSV output.
fixtures/ contains sanitized test data only.
tests/ contains Vitest coverage for parsing, privacy, rendering, exports, and CLI smoke tests.
.agents/skills/codex-usage-heatmap/ contains the reusable Codex Skill for this project.

Development Commands

pnpm dev doctor
pnpm dev scan --json --source fixtures
pnpm dev report --out ./codex-usage-report
pnpm dev sample --out ./tmp/sample-report

Build, Test, and Lint

Always run:

pnpm lint
pnpm typecheck
pnpm test
pnpm build
pnpm check:language

Privacy Rules

Do not read, print, store, or snapshot credentials.
Do not read auth.json, .env, cookies, private keys, token stores, or credential-like files.
Do not include prompt text or response text in reports, snapshots, warnings, or fixtures.
Do not store raw JSONL lines.
Do not add network calls by default.
Redact local absolute paths by default.

Parser Rules

Treat Codex log schemas as unstable.
Prefer parser adapters over hard-coded global assumptions.
Continue after malformed JSONL lines.
Convert cumulative totals to deltas only within the same session.
Skip negative deltas.
Mark estimated events with an explicit estimation mode.

Documentation Rules

Keep public repository content English-only.
Document conservative assumptions in README limitations.
Keep examples sanitized and reproducible.

Read the full file on GitHub · 79 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.

2mo ago First seen · 79 lines · 615 tokens per session scan A 57b71cc0912a

Subscribe to this mod's changes

codex-usage-heatmap AGENTS.md is an instructions file published in the GitHub repository Gatsby007max/codex-usage-heatmap (1 stars, last pushed 5mo ago), licensed MIT. It adds 615 tokens to every session, about $0.0025 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-31.

Analytics and metrics cli codex codex-cli developer-tools github-contributions heatmap

codex-usage-heatmap AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
codex-usage-heatmap AGENTS.mdGatsby007max/codex-usage-heatmap	Instructions file	1	5mo ago	MIT	A	615	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

codex-usage-heatmap: Instructions file for Codex