codex-usage-sidebar AGENTS.md

A project instruction file for a macOS app that shows Codex usage limits, reset times, credits, and bank details.

In plain words
What is it for?
Use it when changing the codex-usage-sidebar project so the work follows its required commands, branch naming, commit rules, and release process.
Why use it?
It gives coding agents the project’s required rules for safe development, branching, testing, releases, and governance checks.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/jacehwang/codex-usage-sidebar/agents-md
Clone the repo
git clone --depth 1 https://github.com/JaceHwang/codex-usage-sidebar

Made for: Codex, OpenCode.

Per session 148 This file is loaded in full into every session.
When invoked 148 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00148 $0.00148
Opus 5 $0.00074 $0.00074
Sonnet 5 $0.00030 $0.00030
Haiku 4.5 $0.00015 $0.00015

Measured 2d ago against content hash 57d9c8d3d69e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

codex-usage-sidebar 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 2d 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 · 12 lines

What it actually says

Repository governance

  • Run ./governance doctor before the first code-changing action in a task. If hooks are inactive, run ./governance bootstrap and repeat doctor.
  • Never develop or commit directly on main; use codex/<type>/<kebab-case>.
  • Use English Conventional Commit headers and Conventional Commit PR titles. PR background and verification may be written in Chinese.
  • Never use --no-verify, weaken checks, overwrite a published release asset, or edit product versions in ordinary commits.
  • Run ./governance check all before pushing. Release product versions only through the generated Release Please PR.
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. 2d ago First seen · 12 lines · 148 tokens per session scan A 57d9c8d3d69e

Subscribe to this mod's changes

codex-usage-sidebar AGENTS.md is an instructions file published in the GitHub repository JaceHwang/codex-usage-sidebar (3 stars, last pushed 2d ago), licensed MIT. It adds 148 tokens to every session, about $0.0007 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.