check

A command that checks whether installed add-ons differ from their recorded versions or available registry versions. A registry is the service that lists published add-on versions.

In plain words
What is it for?
Use it to find add-ons that need updating in a personal or project-specific installation, then update a selected add-on with the related update command.
Why use it?
It shows which installed add-ons have changed or have newer published versions, so updates do not have to be checked manually.

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/rolecraft-sh/rolecraft/check
Clone the repo
git clone --depth 1 https://github.com/rolecraft-sh/rolecraft
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 233 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.00233
Opus 5 $0.00000 $0.00117
Sonnet 5 $0.00000 $0.00047
Haiku 4.5 $0.00000 $0.00023

Measured 3d ago against content hash f1b6a984602a, 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 3d 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.

docs/commands/check.md · 38 lines

What it actually says

rolecraft check

Check installed skills for available updates.

Usage

rolecraft check

Description

Reads the lockfile and compares each skill's stored content hash against the current source. Skills whose content hash differs from the lockfile are flagged as having updates available. Works with both global and project-scoped skills.

If the rolecraft Registry is reachable, check also looks up version information for each installed skill. When a newer version is published in the registry, it shows up in the output with (registry) suffix:

   🔄 testing-guide              v1.0.0 → v1.1.0 (registry)
   ✅ react-rules                up to date

Run rolecraft update <slug> to apply the update.

Example

rolecraft check

Node.js API

This command is also available as a programmatic function. See the Node.js API documentation for detailed usage.

import { check } from 'rolecraft'
const updates = await check()
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. 3d ago First seen · 38 lines · 0 tokens per session scan A f1b6a984602a

Subscribe to this mod's changes

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