update

A command for updating installed skills or tracked code repositories to newer versions. A tracked repository is a project whose source location and update history are recorded.

In plain words
What is it for?
Use it to update one skill, several skills, a skill group, a tracked repository, or everything managed by the tool.
Why use it?
It helps bring in upstream changes while checking for local edits and security concerns before updates are applied.

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/update
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 3,511 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.03511
Opus 5 $0.00000 $0.01755
Sonnet 5 $0.00000 $0.00702
Haiku 4.5 $0.00000 $0.00351

Measured 2d ago against content hash 18020416b217, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

update 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.

website/docs/reference/commands/update.md · 430 lines

How it starts

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

update

Update one or more skills or tracked repositories to the latest version.

skillshare update my-skill           # Update single skill
skillshare update a b c              # Update multiple at once
skillshare update --group frontend   # Update all skills in a group
skillshare update team-skills        # Update tracked repo
skillshare update --all              # Update everything
skillshare update agents --all       # Update all tracked/updatable agents

When to Use

  • A tracked repository has new commits (found via check)
  • An installed skill has a newer version available
  • You want to re-download a skill from its original source

update demo

What Happens

For Tracked Repositories

flowchart TD
    TITLE["skillshare update _team-skills"]
    S1["1. Check for uncommitted changes"]
    S2["2. Run git pull"]
    S3["3. Security audit gate"]
    S4["4. Show changes"]
    TITLE --> S1 -- clean --> S2 --> S3
    S3 -- pass --> S4
    S3 -- "At/above threshold" --> RB["Rollback"]

    style RB fill:#ef4444,color:#fff

For Regular Skills

flowchart TD
    TITLE["skillshare update my-skill"]
    S1["1. Read metadata"]
    S2["2. Re-install from source"]
    S3["3. Security audit gate"]
    TITLE --> S1 --> S2 --> S3

Options

Flag Description
--all, -a Update all tracked repos/skills, or all agents when used as update agents --all
--group, -G <name> Update all updatable skills in a group, or all agents in an agent subdirectory
--force, -f Discard local changes and proceed despite audit findings
--dry-run, -n Preview without making changes
--skip-audit Skip the post-update security audit gate
--audit-threshold <t>, --threshold <t>, -T <t> Override update audit block threshold (`critical
--diff Show file-level change summary after skill/repo update
--audit-verbose Show detailed per-skill audit findings in batch mode
--prune Remove stale skills (deleted upstream) instead of warning
--project, -p Use project-level config in current directory
--global, -g Use global config (~/.config/skillshare)
--json Output as JSON
--help, -h Show help

Read the full file on GitHub · 430 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. 2d ago First seen · 430 lines · 0 tokens per session scan A 18020416b217

Subscribe to this mod's changes

update 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 3,511 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.