A repeatable process for bringing changes from a newer release of the parent career-operations project into its web interface. A parent project is the upstream codebase that this project depends on or mirrors.

Use it when updating the parent project, applying an audit-only fix release, or working from a parent release URL. It guides the update, scopes changes, ports fixes, updates documentation, and runs the required checks.

It prevents a partial update from leaving the web interface out of sync with the parent project. The process also covers documentation, tests, release checks, and parity verification.

parent-sync — Skill for Claude Code and Codex by Fighter90: A repeatable process for bringing changes from a newer…

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 skills/fighter90/career-ops-ui/parent-sync

Any agent

npx skills add Fighter90/career-ops-ui --skill parent-sync

Clone the repo

git clone --depth 1 https://github.com/Fighter90/career-ops-ui

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/fighter90/career-ops-ui/parent-sync.svg)](https://agentmods.dev/skills/fighter90/career-ops-ui/parent-sync)

Your own site

<a href="https://agentmods.dev/skills/fighter90/career-ops-ui/parent-sync"><img src="https://agentmods.dev/badge/skills/fighter90/career-ops-ui/parent-sync.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 3,942 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.

Model	Per session	Once invoked
Fable 5	$0.00083	$0.03942
Opus 5	$0.00042	$0.01971
Sonnet 5	$0.00017	$0.00788
Haiku 4.5	$0.00008	$0.00394

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

Security

Grade A, and why

parent-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 4d 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/parent-sync/SKILL.md · 230 lines

How it starts

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

parent-sync — parity release pipeline

Proven across v1.119.0 (parent 1.19), v1.120.0 (1.20), v1.123.0 (1.21). Each phase below is a hard gate — do not skip, do not reorder. The parent repo (..) is READ-ONLY except the user-authorized git pull itself.

Also covers audit-driven patch releases (no parent delta — e.g. v1.134.1 validation-hardening from a full-project + all-locales audit). Skip Phases 1–2 (no pull, no provider port); Phases 3–7 apply UNCHANGED — QA prompt, docs ×17, site changelog resync, wiki, cross-surface verify are all still mandatory. The count that moves on a fix-only release is usually just the test count.

Phase 1 — Pull & scope

cd .. && git rev-parse HEAD (save OLD), git pull (confirm origin is the fork and you're on main first: git remote get-url origin / git branch --show-current), cat VERSION. Diff by commit range to origin/main HEAD — never by VERSION and never to the career-ops-vX.Y.Z tag. On this fork BOTH lag main: release-please cuts the tag/VERSION behind main, so the fork's HEAD carries post-tag providers/fixes. A pasted release-URL tempts you to OLD..<tag> — that under-scopes (v1.210.0 did exactly this against career-ops-v1.27.0 and missed yourator + the _html-entities/_trust-validator fixes already on HEAD, forcing an extra v1.211.0). Use OLD..origin/main, the HEAD you actually reset/deploy to.
Read the new CHANGELOG entries + git diff OLD..origin/main --name-status. Before porting a MIRROR fix, grep web-ui for the shared idiom first — web-ui is sometimes already AHEAD (its senjob used the shared C0-safe decoder from day one; jobvite already imported it), so the parent's fix is a no-port.
Classify every change:
- providers/*.mjs added → PORT as a web-ui source+adapter (Phase 2).
- Changes to code web-ui MIRRORS (role-matcher, detect-reposts, trust-validator, scan-sanitize, providers already ported, cooldown) → PORT the diff into server/lib/ + port the parent's test cases.
- Scripts web-ui RELAYS read-only (stats.mjs, salary-gap.mjs, analyze-patterns.mjs, followup-*) → usually NO code change (fail-soft relay absorbs shape changes) — note it.
- CLI-only (modes/*.md prompts, updater, doctor, PDF templates, ledger/site infra, dashboard Go TUI) → NOT ported; document in the CHANGELOG Notes section with the reason ("web-ui does not shell into this" or "already covered by X since vY").
- Parent UI/dashboard features (footer links, help entries) → mirror the CONCEPT in the SPA if it's user-facing (precedent: the Manifesto link).

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

4d ago First seen · 230 lines · 83 tokens per session scan A 8e4a0fa86770

Subscribe to this mod's changes

parent-sync is a skill published in the GitHub repository Fighter90/career-ops-ui (60 stars, last pushed today), licensed MIT. It adds 83 tokens to every session and 3,942 once invoked, about $0.0004 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-08-30.

Frontend Git and workflow Writing and docs ashby career-ops claude-code express greenhouse-api hh-ru

parent-sync

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

parent-sync — parity release pipeline

Phase 1 — Pull & scope

What this file has done since we first saw it

Other skills, from other repositories

ui4

triage-ci-flake

audit-dependencies

e2e-write-visual-test

ui4-review

generate-translations