agentleFS
Sign inStart free
gtappsgtapps/claude-code-hermit/.agents/skills/pricing-refresh/SKILL.md

pricing-refresh

Skill84 starsChanged 5 days agoMITView on GitHub

Refresh or verify the hermit cost rate table against Anthropic's live pricing. Use when the operator says "refresh pricing", "verify pricing", "is the rate table current", "new model pricing", or asks whether `scripts/lib/pricing.ts` matches current Codex rates. Maintainer-only; never autonomous, never a routine, never touches operator installs.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read plugins/Codex-hermit/scripts/lib/pricing.ts.

    line 14
  2. Distinctive:

    Stop here unless the operator confirms an edit.

    line 42
  3. Distinctive:

    If the operator explicitly confirms:

    line 46
  4. Very specific:

    Add a ### Fixed bullet under plugins/Codex-hermit/CHANGELOG.md [Unreleased]: rate table refreshed for the current generations.

    line 50
  5. Very specific:

    Do not commit. Do not bump min_claude_code_version.

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Pricing refresh

Compare plugins/Codex-hermit/scripts/lib/pricing.ts to Anthropic's live docs and, only after explicit confirmation, edit the table. Do not run this on a schedule. Do not write anything under an operator's .Codex-hermit/.

Step 1 — Read the table

Read plugins/Codex-hermit/scripts/lib/pricing.ts. Record every PRICING key, its { input, output, cacheRead?, fast? } rates, the CACHE_WRITE_5M / CACHE_WRITE_1H / CACHE_READ multipliers, and PRICING_VERIFIED.

Step 2 — Fetch live sources

Load the bundled Codex-api skill. From its shared/live-sources.md, WebFetch these three URLs:

  • Models Overview
  • Pricing
  • Prompt Caching

Extract current model ids, per-MTok input/output, cache write (5m and 1h) and read multipliers, any per-model cacheRead absolute rate, and fast-mode rates.

Step 3 — Unknown ids in the log

From .Codex-hermit/cost-log.jsonl (this repo's own hermit dir, last 30 days of timestamp), list distinct model values that are not exact PRICING keys (dated <key>-YYYYMMDD snapshots of an existing key count as exact). Print them. Do not edit operator installs.

Step 4 — Diff

Print a rate-diff table: id, live input/output/cache/fast vs the file. Flag missing ids, stale rates, and a PRICING_VERIFIED date that is not today.

Stop here unless the operator confirms an edit.

Step 5 — Edit on confirmation only

If the operator explicitly confirms:

  1. Edit plugins/Codex-hermit/scripts/lib/pricing.ts rates and keys to match the live table. Set PRICING_VERIFIED to today's date (YYYY-MM-DD).
  2. Add a ### Fixed bullet under plugins/Codex-hermit/CHANGELOG.md [Unreleased]: rate table refreshed for the current generations.
  3. Run cd plugins/Codex-hermit && bun test tests/pricing.test.ts.

Do not commit. Do not bump min_claude_code_version. Do not add a hook, a routine, or a config.json entry.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free