Pulling Updates from Skills Repository

Pulling Updates from Skills Repository is a skill for Claude Code from RudyCity/superagent. It costs 21 tokens per session (946 once invoked), scanned A, a copy of Pulling Updates from Skills Repository, MIT.

A guide for updating a local skills repository with changes from the upstream obra/superpowers-skills repository while keeping personal edits.

In plain words
What is it for?
It is for synchronizing a skills repository with its tracked remote and handling uncommitted changes during the update.
Why use it?
It gives a repeatable process for checking local changes, temporarily saving them, fetching updates, and bringing personal work back safely.

Skill for Claude Code

Written for Claude Code: when-to-use in frontmatter. Also seen: installed under .agents/ (shared by several agents).

Good fit It is for synchronizing a skills repository with its tracked remote and handling uncommitted changes during the update.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rudycity/superagent/pulling-updates-from-skills-repository
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.

Any agent
npx skills add RudyCity/superagent --skill pulling-updates-from-skills-repository
Clone the repo
git clone --depth 1 https://github.com/RudyCity/superagent

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.

agentmods badge for Pulling Updates from Skills Repository

README.md
[![agentmods](https://agentmods.dev/badge/skills/rudycity/superagent/pulling-updates-from-skills-repository/github.svg)](https://agentmods.dev/skills/rudycity/superagent/pulling-updates-from-skills-repository)
Your own site
<a href="https://agentmods.dev/skills/rudycity/superagent/pulling-updates-from-skills-repository"><img src="https://agentmods.dev/badge/skills/rudycity/superagent/pulling-updates-from-skills-repository/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.

agentmods 80×15 button for Pulling Updates from Skills Repository

Your own site · 80×15
<a href="https://agentmods.dev/skills/rudycity/superagent/pulling-updates-from-skills-repository"><img src="https://agentmods.dev/badge/skills/rudycity/superagent/pulling-updates-from-skills-repository.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 946 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.
Origin 100% copy Near-identical to another mod 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.1 $0.00021 $0.00946
Opus 5 $0.00010 $0.00473
Sonnet 5 $0.00004 $0.00189
Haiku 4.5 $0.00002 $0.00095

Measured 8d ago against content hash 988109237580, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

Pulling Updates from Skills Repository 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 8d 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.

Origin

This is a copy

100% identical to Pulling Updates from Skills Repository — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/pulling-updates-from-skills-repository/SKILL.md · 139 lines

How it starts

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

Updating Skills from Upstream

Overview

Pull and merge upstream changes from obra/superpowers-skills into your local skills repository while preserving your personal modifications.

Announce at start: "I'm using the Updating Skills skill to sync with upstream."

Prerequisites

Your skills repo must have a tracking branch configured. The plugin sets this up automatically (either as a fork with origin remote, or with an upstream remote).

The Process

Step 1: Check Current Status

Run:

cd ~/.config/superpowers/skills
git status

If working directory is dirty: Proceed to Step 2 (stash changes) If clean: Skip to Step 3

Step 2: Stash Uncommitted Changes (if needed)

Run:

git stash push -m "Temporary stash before upstream update"

Record: Whether changes were stashed (you'll need to unstash later)

Step 3: Determine Tracking Remote and Fetch

First, detect which remote to use:

TRACKING_REMOTE=$(git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null | cut -d'/' -f1 || echo "")

Then fetch from the appropriate remote:

if [ -n "$TRACKING_REMOTE" ]; then
    git fetch "$TRACKING_REMOTE" 2>/dev/null || true
else
    git fetch upstream 2>/dev/null || git fetch origin 2>/dev/null || true
fi

Expected: Fetches latest commits from the tracking remote (or falls back to upstream/origin)

Step 4: Check What's New

Run:

git log HEAD..@{u} --oneline

Show user: List of new commits being pulled

Note: @{u} refers to the upstream tracking branch for your current branch

Step 5: Merge Changes

First, try a fast-forward merge (cleanest option):

git merge --ff-only @{u}

If fast-forward succeeds: Skip to Step 7 (no conflicts possible with fast-forward) If fast-forward fails: Your branch has diverged. Try regular merge:

git merge @{u}

If merge succeeds cleanly: Proceed to Step 7 If conflicts occur: Proceed to conflict resolution

Step 6: Handle Merge Conflicts (if any)

Read the full file on GitHub · 139 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. 8d ago First seen · 139 lines · 21 tokens per session scan A 988109237580

Subscribe to this mod's changes

Pulling Updates from Skills Repository is a skill published in the GitHub repository RudyCity/superagent (21 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 946 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to Pulling Updates from Skills Repository, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

prowler-commit

Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.

prowler-cloud/prowler · 33 tokens

gh-auth-isolation

Safely manage multiple GitHub identities (EMU + personal) in agent workflows.

github/gh-aw · 20 tokens

comet-github

A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.

rpamis/comet · 72 tokens

github-skill

Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.

zeenie-ai/OpenCompany · 51 tokens

changelog-composer

Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".

Mathews-Tom/armory · 67 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens