check

A read-only check for updates to tracked code repositories and installed skills.

In plain words
What is it for?
Checking one or more skills, repository commit status, deleted upstream skill folders, and update status in continuous-integration jobs.
Why use it?
It shows what is outdated before anything is changed, so you can review pending updates first.

Command

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 commands/runkids/skillshare/check
Clone the repo
git clone --depth 1 https://github.com/runkids/skillshare
Per session 0 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,555 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.01555
Opus 5 $0.00000 $0.00777
Sonnet 5 $0.00000 $0.00311
Haiku 4.5 $0.00000 $0.00155

Measured yesterday against content hash 1d9b615e9329, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

check 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 yesterday.

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.

website/docs/reference/commands/check.md · 183 lines

How it starts

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

check

Check for available updates to tracked repositories and installed skills without applying changes.

skillshare check                      # Check all repos and skills
skillshare check my-skill             # Check a single skill
skillshare check a b c                # Check multiple skills
skillshare check --group frontend     # Check all skills in frontend/
skillshare check x -G backend         # Mix names and groups
skillshare check --json               # Machine-readable output

When to Use

Before Updating

Preview what would change before running update:

skillshare check         # See what has updates
skillshare update --all  # Apply updates
skillshare sync          # Distribute changes

CI/CD Pipeline

Check for stale skills in CI:

result=$(skillshare check --json)
# Parse JSON to detect outdated skills

What It Does

check inspects your source directory and reports update status for:

  1. Tracked repositories — Fetches from origin, shows how many commits you're behind
  2. Installed skills (with metadata) — Compares installed version against the remote HEAD
  3. Stale skills — Detects skills whose subdirectory was deleted from the upstream repository
  4. Local skills — Marks as "local source" (no remote to compare)
  5. Skill-level targets validation — Warns about unknown target names in SKILL.md targets frontmatter fields

Unlike update, check never modifies any files.

Example Output

skillshare check

  Tracked Repos
  ─────────────────────────────────────────
  ✓ _team-skills       up to date
  ⬇ _shared-rules      3 commits behind
  ! _design-system     has uncommitted changes

  Installed Skills (remote)
  ─────────────────────────────────────────
  ✓ pdf                up to date          anthropics/skills
  ⬇ commit             update available    anthropics/skills
  ⚠ old-helper         stale (deleted upstream)
  • local-skill        local source

  ⚠ 1 skill(s) stale (deleted upstream) — run 'skillshare update --all --prune' to remove
  Summary: 1 repo + 1 skill have updates available
  Run 'skillshare update <name>' or 'skillshare update --all'

Read the full file on GitHub · 183 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. yesterday First seen · 183 lines · 0 tokens per session scan A 1d9b615e9329

Subscribe to this mod's changes

check is a command published in the GitHub repository runkids/skillshare (2,597 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,555 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-30.