claude-code-scenes: Skill for Claude Code

.claude/skills/sync-upstream/SKILL.md

sync-upstream is a skill for Claude Code from rezathepure/claude-code-scenes. It costs 58 tokens per session (2,304 once invoked), scanned A, original, no licence file.

A workflow for updating a code fork from its original repository, called the upstream repository.

In plain words
What is it for?
Use it to check for upstream updates, pull them into the fork, and merge the latest changes.
Why use it?
It helps determine whether the fork is behind and bring in changes from the original project.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is rezathepure/claude-code-scenes's own configuration. It tells Claude Code how to work on claude-code-scenes itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-code-scenes configures →

Reuse

Borrowing it

Nothing to install: this file belongs to rezathepure/claude-code-scenes. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/rezathepure/claude-code-scenes/main/.claude/skills/sync-upstream/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/rezathepure/claude-code-scenes

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 sync-upstream

README.md
[![agentmods](https://agentmods.dev/badge/skills/rezathepure/claude-code-scenes/sync-upstream/github.svg)](https://agentmods.dev/skills/rezathepure/claude-code-scenes/sync-upstream)
Your own site
<a href="https://agentmods.dev/skills/rezathepure/claude-code-scenes/sync-upstream"><img src="https://agentmods.dev/badge/skills/rezathepure/claude-code-scenes/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.

agentmods 80×15 button for sync-upstream

Your own site · 80×15
<a href="https://agentmods.dev/skills/rezathepure/claude-code-scenes/sync-upstream"><img src="https://agentmods.dev/badge/skills/rezathepure/claude-code-scenes/sync-upstream.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,304 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 unknown 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.1 $0.00058 $0.02304
Opus 5.5 $0.00023 $0.00922
Sonnet 5.5 $0.00012 $0.00461
Haiku 4.5 $0.00006 $0.00230

Measured 1mo ago against content hash 089b4813c633, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 1mo 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.

.claude/skills/sync-upstream/SKILL.md · 191 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

Read it on GitHub

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. 1mo ago First seen · 191 lines · 58 tokens per session scan A 089b4813c633

Subscribe to this mod's changes

sync-upstream is a skill published in the GitHub repository rezathepure/claude-code-scenes (10 stars, last pushed 2mo ago), with no licence file. It adds 58 tokens to every session and 2,304 once invoked, about $0.0002 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-31.

Related

Other skills, from other repositories

safe-extraction

Apply when extracting code from a large monolith file into submodules. Covers barrel re-exports, internals DI seam proxy patterns, CI invariant allowlist updates, and cross-file test verification. Prevents CI failures, broken imports, and test regressions from code extraction.

ZaxbyHub/opencode-swarm · 60 tokens

git-revert-safety

Apply when reverting commits, undoing merges, or recovering from branch contamination. Covers collateral damage verification (manifest, package.json, CHANGELOG, lockfiles), cherry-pick vs revert decision matrix, partial-revert detection, merge-parent handling, and post-revert CI verification. Prevents the most common…

ZaxbyHub/opencode-swarm · 79 tokens

commit-pr

Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…

ZaxbyHub/opencode-swarm · 100 tokens

parallel-work-check

Apply before starting work on an existing branch. Checks for parallel work by other agents or developers that may supersede or conflict with your planned changes. Prevents wasted effort on stale branches.

ZaxbyHub/opencode-swarm · 41 tokens

fork-pr-operations

Operational patterns for fork PRs (head repo differs from base repo). Covers GitHub workflow approval after push, force-push protocol, remote naming conventions, stale CI verification, and bot review multi-round awareness. Load when working with fork PRs, cross-repo contributions, or workflow approval issues.

ZaxbyHub/opencode-swarm · 65 tokens

merge-queue-readiness

Pre-queue merge-group CI simulation. Triggered before adding a PR to a GitHub merge queue. Prevents merge-queue kick-outs from integration test failures.

ZaxbyHub/opencode-swarm · 39 tokens