Borrowing it
Nothing to install: this file belongs to prefect12/codex-token-meter. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/prefect12/codex-token-meter/main/AGENTS.mdgit clone --depth 1 https://github.com/prefect12/codex-token-meterWrote 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/prefect12/codex-token-meter/agents-md)<a href="https://agentmods.dev/instructions/prefect12/codex-token-meter/agents-md"><img src="https://agentmods.dev/badge/instructions/prefect12/codex-token-meter/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.
<a href="https://agentmods.dev/instructions/prefect12/codex-token-meter/agents-md"><img src="https://agentmods.dev/badge/instructions/prefect12/codex-token-meter/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.01357 | $0.01357 |
| Opus 5.5 | $0.00543 | $0.00543 |
| Sonnet 5.5 | $0.00271 | $0.00271 |
| Haiku 4.5 | $0.00136 | $0.00136 |
Grade A, and why
codex-token-meter 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 1mo 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Token Meter Development Guide
Project Shape
- This is a native macOS menu bar app built directly with
swiftc. - The app entrypoint lives in
Sources/CodexTokenMeter/main.swift; supporting code is split into focused files under the same directory. - The companion Task Bar app lives in
Sources/CodexPetBar/main.swiftand is part of the same product family, not a separate design surface. build.shcompiles every Swift file underSources/CodexTokenMeter, so future file splits do not need build-script changes.- Prefer small, behavior-preserving changes unless you are explicitly doing a planned refactor.
- Read
docs/ARCHITECTURE.mdbefore changing parser, quota, cost, or UI behavior.
Build And Verification
- Compile check:
./build.sh - CLI parser check:
"./build/AI Token Meter.app/Contents/MacOS/CodexTokenMeter" --print --window=week --quota=all - Live quota check:
"./build/AI Token Meter.app/Contents/MacOS/CodexTokenMeter" --print-live - Service-status check:
"./build/AI Token Meter.app/Contents/MacOS/CodexTokenMeter" --print-service-status - Dashboard render check for UI changes:
"./build/AI Token Meter.app/Contents/MacOS/CodexTokenMeter" --render-dashboard=/tmp/ai-token-meter-dashboard.png
--print-live, --print-profile, --print-service-status, and dashboard rendering can depend on Codex login state or network availability. Do not treat their unavailability as a compile regression unless the failure is caused by local code.
Git Workflow
- Prefer merging changes through pull requests. Do not merge directly into
mainunless the user explicitly asks for it. - All source, behavior, or UI changes must use this sequence: a focused branch → PR → merged
main→ fetchorigin/main→ build and install from that exact merged revision. Do not install an unmerged working-tree build as the delivered app. - Before calling a change complete, verify the PR merge, confirm local
HEADequalsorigin/main, then run the relevant checks and validate the installed/Applications/AI Token Meter.appsurface.
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.
- 1mo ago First seen · 76 lines · 1,357 tokens per session scan A d77e8555cbe1
codex-token-meter AGENTS.md is an instructions file published in the GitHub repository prefect12/codex-token-meter (9 stars, last pushed 9d ago), licensed MIT. It adds 1,357 tokens to every session, about $0.0054 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.
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).
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.
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).
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.
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).
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.