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 skills/cintia09/codenook/model-probenpx skills add cintia09/CodeNook --skill model-probegit clone --depth 1 https://github.com/cintia09/CodeNookWhat 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.00000 | $0.00697 |
| Opus 5 | $0.00000 | $0.00349 |
| Sonnet 5 | $0.00000 | $0.00139 |
| Haiku 4.5 | $0.00000 | $0.00070 |
Grade A, and why
model-probe 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
model-probe (builtin skill)
Role
Discover available LLM models in the current runtime, classify each into
the three tiers (strong / balanced / cheap), and write the resulting
catalog so config-resolve can expand tier_* symbols. Implements
architecture §3.2.4.2 (Model Discovery & Tiering).
Triggers
init.sh --refresh-models(manual)init.sh --install-plugin/--upgrade-core(auto on install events)- Workspace catalog older than
ttl_days(auto-refresh in M2+) - Main session "刷新模型" natural-language command (M2+)
Probe sources (in order)
- Runtime API — Claude Code
list_models()/ Copilot CLI registry. M1: not implemented; falls through to source 2. CODENOOK_AVAILABLE_MODELSenv var — comma-separated model ids.- Builtin fallback — minimum viable triple (
opus-4.7,sonnet-4.5,haiku-4.5).
The runtime label is set to "env", "builtin-fallback", or one of the
runtime names as appropriate.
CLI
probe.sh print catalog JSON to stdout
probe.sh --output <file> write catalog JSON to <file>
probe.sh --tier-priority <yaml_file> override built-in priority
probe.sh --check-ttl <file> --ttl-days <int> exit 0 if fresh, 1 if stale
Any catastrophic probe error (e.g. unreadable --tier-priority file) →
stderr starts with probe failed: and exits non-zero.
Tier classification
Each model id is matched against tier_priority (user-supplied or
built-in). The model's tier is the first priority bucket containing it.
resolved_tiers.<tier> is the first id from tier_priority[tier] that is
also in available.
Built-in tier_priority mirrors implementation.md §3.5.1.2:
strong: [opus-4.7, opus-4.6, sonnet-4.6, gpt-5.4]
balanced: [sonnet-4.6, sonnet-4.5, gpt-5.4, gpt-5.4-mini]
cheap: [haiku-4.5, gpt-5.4-mini, gpt-4.1, sonnet-4.5]
Output schema
{
"refreshed_at": "ISO-8601 UTC",
"ttl_days": 30,
"runtime": "env | builtin-fallback | claude-code | copilot-cli",
"available": [
{"id": "opus-4.7", "tier": "strong", "cost": "high", "provider": "anthropic"}
],
"resolved_tiers": { "strong": "opus-4.7", "balanced": "sonnet-4.6", "cheap": "haiku-4.5" },
"tier_priority": { "strong": [...], "balanced": [...], "cheap": [...] }
}
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 68 lines · 0 tokens per session scan A 1563bffa1d8c
model-probe is a skill published in the GitHub repository cintia09/CodeNook (5 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 697 tokens. 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…