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/gatsby007max/codex-usage-heatmap/agents-mdgit clone --depth 1 https://github.com/Gatsby007max/codex-usage-heatmapWrote 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/gatsby007max/codex-usage-heatmap/agents-md)<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="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 | $0.00615 | $0.00615 |
| Opus 5 | $0.00308 | $0.00308 |
| Sonnet 5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00061 | $0.00061 |
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 3d 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 — 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.tswires 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 doctorpnpm dev scan --json --source fixturespnpm dev report --out ./codex-usage-reportpnpm dev sample --out ./tmp/sample-report
Build, Test, and Lint
Always run:
pnpm lintpnpm typecheckpnpm testpnpm buildpnpm 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.
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.
- 3d ago First seen · 79 lines · 615 tokens per session scan A 57b71cc0912a
codex-usage-heatmap AGENTS.md is an instructions file published in the GitHub repository Gatsby007max/codex-usage-heatmap (1 stars, last pushed 3mo ago), licensed MIT. It adds 615 tokens to every session, about $0.0031 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-31.
Other instructions, from other repositories
apm python.instructions.md
Python development guidelines.
CodexPotter AGENTS.md
Instructions for breezewish/CodexPotter, covering repository guidelines, workflow principles, engineering rules, core principles: simplicity & readability and better maintainability.
OpenMicro AGENTS.md
Instructions for stephenleo/OpenMicro, covering openmicro — project conventions and releases.
squarebox CLAUDE.md
Instructions for SquareWaveSystems/squarebox, covering claude.md, agent skills, issue tracker, triage labels and domain docs.
codmate AGENTS.md
Instructions for loocor/codmate, a project described as: CodMate is a macOS SwiftUI app for managing CLI AI sessions: browse, search, organize, resume, and review work produced by Codex, Claude Code, and Gemini CLI. It focuses on speed, a compact three-column UI, and “ship it” workflows like Project Review (Git…
CodexBar AGENTS.md
AGENTS.md instructions for bob-zebedy/CodexBar, covering repository guidelines, 项目结构与模块组织, 构建、测试与开发命令, 写作风格 and 代码和注释.