What is check-sdk-updates?

A version-checking guide for Claude Code, Claude Agent SDK, and Codex SDK packages listed in package.json. It compares the declared versions with the latest versions published on npm.

Use it to check SDK and CLI updates in a project and identify packages whose declared versions are behind the latest npm releases.

It removes the need to check each package and npm release separately. It shows which SDKs or command-line tools may need updating.

How tony1223/better-agent-terminal configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to tony1223/better-agent-terminal. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/tony1223/better-agent-terminal/main/.claude/skills/check-sdk-updates/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/tony1223/better-agent-terminal

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/tony1223/better-agent-terminal/check-sdk-updates/github.svg)](https://agentmods.dev/skills/tony1223/better-agent-terminal/check-sdk-updates)

Your own site

<a href="https://agentmods.dev/skills/tony1223/better-agent-terminal/check-sdk-updates"><img src="https://agentmods.dev/badge/skills/tony1223/better-agent-terminal/check-sdk-updates/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/tony1223/better-agent-terminal/check-sdk-updates"><img src="https://agentmods.dev/badge/skills/tony1223/better-agent-terminal/check-sdk-updates.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 917 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00065	$0.00917
Opus 5.5	$0.00026	$0.00367
Sonnet 5.5	$0.00013	$0.00183
Haiku 4.5	$0.00006	$0.00092

Measured 1mo ago against content hash 90991fc1d58f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

check-sdk-updates 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.

.claude/skills/check-sdk-updates/SKILL.md · 65 lines

How it starts

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

Check SDK Updates

Compare the versions of @anthropic-ai/claude-code, @anthropic-ai/claude-agent-sdk, and @openai/codex-sdk declared in package.json against the latest published version on npm.

Steps

Read the dependencies block of package.json and extract the current declared range for each of:
- @anthropic-ai/claude-code
- @anthropic-ai/claude-agent-sdk
- @openai/codex-sdk
Run the following command (single Bash call) to fetch latest versions in parallel:
```
npm view @anthropic-ai/claude-code version & \
npm view @anthropic-ai/claude-agent-sdk version & \
npm view @openai/codex-sdk version & \
wait
```
Map the three lines of output back to the three packages in the order requested.

For each package, compare the declared version (strip leading ^/~) with the latest. Report a compact table:

Package                              Current    Latest     Status
@anthropic-ai/claude-code            2.1.119    2.1.120    ⬆ update
@anthropic-ai/claude-agent-sdk       0.2.119    0.2.119    ✓ up to date
@openai/codex-sdk                    0.125.0    0.126.0    ⬆ update

For each outdated package, analyze the gap between current and latest so the user can decide how to implement the update. For each one:

a. Get the list of versions in between with:
```
npm view <pkg> versions --json
```
Filter to versions strictly greater than current and ≤ latest. Note the count and span (patch / minor / major bumps).

b. Try to fetch release notes / changelog. Try in this order, stop at the first that works:
- npm view <pkg> repository.url → if it points to a GitHub repo, use gh release list -R <owner/repo> --limit 30 and gh release view <tag> -R <owner/repo> for the relevant tags.
- Look for a CHANGELOG.md inside node_modules/<pkg>/ (already-installed copy reflects the current version, but its history section may still cover newer versions if upstream backfills).
- Fall back to: npm view <pkg>@<latest> --json and read the description / homepage fields, then WebFetch the homepage's changelog/releases page.

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

1mo ago First seen · 65 lines · 65 tokens per session scan A 90991fc1d58f

Subscribe to this mod's changes

check-sdk-updates is a skill published in the GitHub repository tony1223/better-agent-terminal (519 stars, last pushed 5d ago), licensed MIT. It adds 65 tokens to every session and 917 once invoked, about $0.0003 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-30.

Claude Code ai-agent anthropic claude developer-tools electron

electron-expert

Expert in Electron framework, desktop app development, IPC, and cross-platform packaging. Use when the user mentions desktop, Node.js, cross platform, Windows, macOS, or Linux, or when the task involves Electron Architecture, Process Types, IPC Communication, or App Lifecycle.

personamanagmentlayer/pcl · 59 tokens

better-agent-terminal: Skill for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Check SDK Updates

Steps

What this file has done since we first saw it

Other skills, from other repositories

electron-expert

feishu-create-doc

feishu-bitable

feishu-calendar

feishu-im-read

feishu-task