What is customize-upstream-sync?

A workflow for bringing the latest changes from the main AIWG repository into your fork and rebuilding it. An upstream remote is a Git connection pointing to the original repository.

Use it to update an AIWG fork, preview incoming upstream changes, or check whether new upstream commits are available.

It removes the manual steps of fetching updates, checking what changed, resolving conflicts, and rebuilding while keeping your own customizations.

customize-upstream-sync — Skill for Claude Code and Codex by jmagly

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 jmagly/aiwg --skill customize-upstream-sync

Clone the repo

git clone --depth 1 https://github.com/jmagly/aiwg

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/jmagly/aiwg/customize-upstream-sync/github.svg)](https://agentmods.dev/skills/jmagly/aiwg/customize-upstream-sync)

Your own site

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

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

When invoked 1,102 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.00024	$0.01102
Opus 5	$0.00012	$0.00551
Sonnet 5	$0.00005	$0.00220
Haiku 4.5	$0.00002	$0.00110

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

Security

Grade A, and why

customize-upstream-sync 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 9d 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.

agentic/code/addons/aiwg-utils/skills/customize-upstream-sync/SKILL.md · 130 lines

How it starts

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

Customize Upstream Sync

You pull the latest upstream AIWG changes into the user's fork, handle conflicts (preserving user customizations), rebuild, and report what changed. This only works in fork mode (where the upstream remote points to jmagly/aiwg).

Triggers

"sync my AIWG"
"pull in the latest AIWG updates"
"update my fork"
"update my AIWG from upstream"
"what's new in upstream AIWG?"
"pull upstream changes"
"get the latest AIWG"

Trigger Patterns Reference

Pattern	Example	Action
Sync request	"sync my AIWG"	Full upstream sync + rebuild
Check only	"what's new in upstream?"	Fetch + diff summary, no merge
Update request	"update my fork"	Full upstream sync + rebuild

Behavior

When triggered:

Verify fork mode — upstream remote must exist:
```
git -C <edgePath> remote get-url upstream
```
If no upstream remote, explain: "This only works if you forked AIWG. Your clone doesn't have an upstream remote. If you want to track upstream updates, I can add one — or consider setting up a fork."
Show what's incoming (before merging):
```
git -C <edgePath> fetch upstream
git -C <edgePath> log HEAD..upstream/main --oneline
```
Report: "Here's what upstream has (N commits):" with the log summary.
If check-only ("what's new") — stop here. Don't merge unless user confirms.
Merge:
```
git -C <edgePath> merge upstream/main
```
Handle conflicts:
- If clean merge: proceed to rebuild
- If conflicts: run git -C <edgePath> diff --name-only --diff-filter=U
- For each conflicted file:
  - If it's a user-added file (new file, not in upstream): auto-resolve keeping user's version
  - If it's an upstream file the user also modified: pause and show the diff, ask which version to keep
- After all conflicts resolved: git -C <edgePath> commit --no-edit

Rebuild and redeploy:

npm --prefix <edgePath> run build
aiwg use all

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

9d ago First seen · 130 lines · 24 tokens per session scan A bf46f7a4e40c

Subscribe to this mod's changes

customize-upstream-sync is a skill published in the GitHub repository jmagly/aiwg (211 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 1,102 once invoked, about $0.0001 per session on Opus 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-09-03.

Autonomous Agents Building agents Claude Code Git and workflow Multi-Agent agentic-coding anthropic developer-tools

autoship

Runs a changesets npm release through the version PR, CI publish, and registry verification. Use when asked to "release this package", "autoship", "merge Version Packages", or diagnose a release that did not publish. For feature PRs use pr-creator or pr-babysitter.

mblode/agent-skills · 63 tokens

sync-references

Pull latest changes from origin for all git repos under a directory. Use when asked to update, sync, or pull reference projects.

LeeJuOh/claude-code-zero · 30 tokens

git-ai-archaeology

Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.

FlorianBruniaux/claude-code-plugins · 47 tokens

ci-pipeline

Push current branch and return the pipeline tracking URL (GitLab or GitHub Actions).

FlorianBruniaux/claude-code-plugins · 21 tokens

publish

Bump version, build, test, publish to npm, and install locally.

eric-cielo/moflo · 17 tokens

intuitive-port-worktree

Port changes from one git worktree or checkout into the default repository folder's current branch, then by default sync the result to the remote default branch when everything is clean. Use when the user asks to move, copy, transfer, transplant, cherry-pick, apply a patch, or port worktree changes into the…

MiaoDX/intuitive-flow · 79 tokens