refresh-specs

refresh-specs is a command for Claude Code from OSideMedia/higgsfield-ai-prompt-skill. It costs 38 tokens per session (1,562 once invoked), scanned A, original, MIT.

A guided command for refreshing saved information about available Higgsfield image, video, audio, and 3D models. It compares the catalogue with the live command-line tool and records the results.

In plain words
What is it for?
Use it after a reported catalogue change or stale snapshot to collect complete model lists, sync specifications, and check evaluation gates on a branch.
Why use it?
It detects specification changes without generating media or spending credits, helping keep local model information current.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md.

Good fit Use it after a reported catalogue change or stale snapshot to collect complete model lists, sync specifications, and check evaluation gates on a branch.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/osidemedia/higgsfield-ai-prompt-skill/refresh-specs
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.

Clone the repo
git clone --depth 1 https://github.com/OSideMedia/higgsfield-ai-prompt-skill

Made for: Claude Code.

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.

agentmods badge for refresh-specs

README.md
[![agentmods](https://agentmods.dev/badge/commands/osidemedia/higgsfield-ai-prompt-skill/refresh-specs/github.svg)](https://agentmods.dev/commands/osidemedia/higgsfield-ai-prompt-skill/refresh-specs)
Your own site
<a href="https://agentmods.dev/commands/osidemedia/higgsfield-ai-prompt-skill/refresh-specs"><img src="https://agentmods.dev/badge/commands/osidemedia/higgsfield-ai-prompt-skill/refresh-specs/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.

agentmods 80×15 button for refresh-specs

Your own site · 80×15
<a href="https://agentmods.dev/commands/osidemedia/higgsfield-ai-prompt-skill/refresh-specs"><img src="https://agentmods.dev/badge/commands/osidemedia/higgsfield-ai-prompt-skill/refresh-specs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,562 The whole file, excluding the scripts and references it only reads on demand.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00038 $0.01562
Opus 5.5 $0.00015 $0.00625
Sonnet 5.5 $0.00008 $0.00312
Haiku 4.5 $0.00004 $0.00156

Measured 19d ago against content hash ec350d66ec5e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

refresh-specs 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 19d 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.

.claude/commands/refresh-specs.md · 96 lines

How it starts

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

The whole Tier-2 refresh as one guided run (CLAUDE.md § Rules → "Spec refreshes"). Run it when the weekly spec-drift tripwire reports CHANGE, when a spec snapshot nears 30 days, or on request. Work on a branch, never on main.

Hard limits for this command: read-only catalog calls only — models_explore (action=list) on the Higgsfield MCP and higgsfield model list|get, higgsfield --version on the CLI. Never call a generate_* tool or higgsfield generate; nothing here spends credits.

Steps — stop at the first failure and report it:

  1. Dump the catalog, verbatim, per type. Call models_explore with action=list for each type: video, image, audio, 3d. Write each response UNCHANGED (no reformatting, no trimming) to

    • specs/models_explore_snapshot_<YYYY-MM-DD>.json (video)
    • specs/models_explore_snapshot_<type>_<YYYY-MM-DD>.json (image / audio / 3d) using today's date. If a response says has_more: true, it is one page of a paginated list — do not write it as a snapshot. Fetch the complete list; if that is not possible, stop and report (sync_specs.py refuses a partial dump anyway).
  2. Sync each type: python3 scripts/sync_specs.py --type video (then image, audio, 3d). Read the stderr WARN lines: an "unmapped" claim or a duration "sentinel" warning means prose the generator would not guess at — report each one. New retired ids are printed as "tombstoned" (they are appended to specs/retired-model-ids.json; never delete entries).

  3. Structural cross-check against the live CLI: python3 scripts/snapshot_crosscheck.py (read-only model list/get). It compares, per model in both sources, every snapshot enum option and default with higgsfield model get --json, every CLI enum with the snapshot, aspect ratios, and media roles — and, per type, catalog membership (a model only one source lists: snapshot-only / cli-only). A snapshot-only model that model list hides but model get answers is compared structurally too. For each ✗ DISAGREE decide:

    • the snapshot is wrong or incomplete → re-dump (step 1), or
    • it is a known representation difference → add an entry to specs/crosscheck_allowlist.json naming model, field, kind, the date seen, and the exact detail the checker printed, plus a note; for a membership difference, verify the id live first (higgsfield model get <id> --json) and add model, kind (snapshot-only | cli-only), type, seen and a note saying why (MCP-only id, list-hidden studio model, CLI-only variant or utility). Remove every entry reported as STALE (a stale entry fails the run). The check must exit 0 before you continue: exit 3 (UNCHECKED — a type with no snapshot or zero models in both sources, or a CLI pull/shape failure) is never a pass. Known CLI↔MCP disagreements already allowlisted (seen 2026-09-26): gpt_image_2 defaults (resolution 1k vs 2k, quality low vs high), aspect ratios (CLI adds 4:5/5:4/auto) and media roles (mask); soul_cinematic soul_id (MCP-only); role naming image (MCP) vs image_references (CLI) on image_auto, soul_cinematic, image_to_3d, multi_image_to_3d, sam_3_3d; and 23 membership differences (MCP-only ids such as sync_so / soul_2 / meshy_*; studio models model list hides but model get answers; the CLI-only nano_banana_2 variants, nano_banana_flash, text2image_soul_v2, depth_anything_video, fps_boost). Note: the CLI has no model list --3d flag — 3d rows come from the unfiltered list by their type field.
  4. Audit the eval cases for moved models (v3.11.3 lesson): python3 scripts/sync_specs.py --type <t> --changed for each type lists models added / removed / changed since the previous snapshot and every evals/cases/ entry that names them (by id or display name). Open each listed case, check its claims against the new specs, and fix it in the same PR.

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

  1. 19d ago First seen · 96 lines · 38 tokens per session scan A ec350d66ec5e

Subscribe to this mod's changes

refresh-specs is a command published in the GitHub repository OSideMedia/higgsfield-ai-prompt-skill (750 stars, last pushed 20d ago), licensed MIT. It adds 38 tokens to every session and 1,562 once invoked, about $0.0002 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-09-28.