What is superpowers-sync-upstream?

A maintenance guide for keeping a local port of two upstream code projects aligned with their source repositories. It checks pinned commits and watched files for changes, then guides re-porting and verification.

Use it to detect upstream changes, compare revisions, classify added, edited, or removed skills, and update the port’s recorded upstream versions.

It reduces the chance that the port silently falls behind upstream fixes or additions. It also gives a repeatable way to investigate reported drift.

superpowers-sync-upstream — Skill by christopherarter

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 christopherarter/superpowers-reasonix --skill superpowers-sync-upstream

Clone the repo

git clone --depth 1 https://github.com/christopherarter/superpowers-reasonix

Made for: Claude Code, Codex.

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/christopherarter/superpowers-reasonix/superpowers-sync-upstream/github.svg)](https://agentmods.dev/skills/christopherarter/superpowers-reasonix/superpowers-sync-upstream)

Your own site

<a href="https://agentmods.dev/skills/christopherarter/superpowers-reasonix/superpowers-sync-upstream"><img src="https://agentmods.dev/badge/skills/christopherarter/superpowers-reasonix/superpowers-sync-upstream/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/christopherarter/superpowers-reasonix/superpowers-sync-upstream"><img src="https://agentmods.dev/badge/skills/christopherarter/superpowers-reasonix/superpowers-sync-upstream.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 851 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.00031	$0.00851
Opus 5.5	$0.00012	$0.00340
Sonnet 5.5	$0.00006	$0.00170
Haiku 4.5	$0.00003	$0.00085

Measured 12d ago against content hash 71441ce28624, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

superpowers-sync-upstream 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 12d 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.

skills/superpowers-sync-upstream/SKILL.md · 57 lines

How it starts

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

Sync Upstream

Re-aligns this port with its two upstreams and re-pins UPSTREAM.json. Run when asked to sync or update from upstream, or after the upstream-drift CI issue fires.

1. Detect

Read UPSTREAM.json for the pinned commits and watched paths, then see what moved:

Do not run .github/scripts/check-upstream-drift.mjs for a read-only check: it can create or update the tracking issue. Inspect the pinned SHAs with git ls-remote or gh api repos/<owner>/<repo>/commits/<branch>, then compare the two endpoints with Git. Use the issue-writing script only when updating the tracker is intended.

For full diffs, shallow-fetch and compare from the pins:

Fetch both the pinned commit and current default-branch head into a temporary blobless clone, then run git diff --no-renames <pin> <head> -- skills/. A GitHub compare API response with 300 files may be truncated; do not treat it as complete.

For Reasonix, diff the pin against main-v2 over internal/tool internal/hook internal/skill internal/frontmatter internal/command. Inspect actual tool registration and implementation together; a declared identity alone does not prove a callable tool exists.

Network blocked? web_fetch the GitHub compare page: <repo>/compare/<pinned>...<branch>, and label incomplete file lists. This step is read-only; dispatch it to a task subagent when appropriate and keep only the drift report to save context.

2. Classify content drift

For each changed obra skill, decide edited, new, or removed.

New skill: port it only if no native Reasonix tool already covers it (task, review, wait, explore). Otherwise add it to UPSTREAM.json retired with a one-line reason.
Removed upstream skill: consider retiring the port equivalent.

3. Re-port

Load superpowers-writing-skills. For each edited or to-be-ported skill, apply the Adaptations rules: snake_case tool names (read_file, edit_file, bash), description rewritten as a forceful imperative within the 130-char index budget, references/* auto-fold, native-tool substitution, path renames (docs/reasonix/...). Preserve the disciplines verbatim: Iron Laws, red-flag tables, RED-GREEN-REFACTOR. Keep bodies lean enough for the flash model.

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

12d ago Changed 71441ce28624
1mo ago First seen · 57 lines · 31 tokens per session scan A 5bf6be7d64e3

Subscribe to this mod's changes

superpowers-sync-upstream is a skill published in the GitHub repository christopherarter/superpowers-reasonix (102 stars, last pushed 12d ago), licensed MIT. It adds 31 tokens to every session and 851 once invoked, about $0.0001 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.

Building agents Git and workflow deepseek reasonix skills

prepare-release

Prepare a new release by collecting commits, generating bilingual release notes, updating version files, and creating a release branch. Use when asked to prepare/create a release, bump version, or run /prepare-release.

CherryHQ/cherry-studio · 44 tokens

gh-create-pr

Create or update GitHub pull requests using the repository-required workflow and template compliance. Use when asked to create/open/update a PR so the assistant reads .github/pullrequesttemplate.md, fills every template section, preserves markdown structure exactly, and marks missing data as N/A or None instead of…

CherryHQ/cherry-studio · 65 tokens

superpowers-sync-upstream