Borrowing it
Nothing to install: this file belongs to Fighter90/career-ops-ui. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Fighter90/career-ops-ui/main/.opencode/command/parent-sync.mdgit clone --depth 1 https://github.com/Fighter90/career-ops-uiWrote 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.
[](https://agentmods.dev/commands/fighter90/career-ops-ui/parent-sync)<a href="https://agentmods.dev/commands/fighter90/career-ops-ui/parent-sync"><img src="https://agentmods.dev/badge/commands/fighter90/career-ops-ui/parent-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.
<a href="https://agentmods.dev/commands/fighter90/career-ops-ui/parent-sync"><img src="https://agentmods.dev/badge/commands/fighter90/career-ops-ui/parent-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00018 | $0.00060 |
| Opus 5.5 | $0.00007 | $0.00024 |
| Sonnet 5.5 | $0.00004 | $0.00012 |
| Haiku 4.5 | $0.00002 | $0.00006 |
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 20d 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.
What it actually says
Follow .claude/skills/parent-sync/SKILL.md exactly (Phase 0 divergence checks first), then ship with
the release agent. $ARGUMENTS
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.
- 20d ago First seen · 6 lines · 18 tokens per session scan A 315f5669e9a5
parent-sync is a command published in the GitHub repository Fighter90/career-ops-ui (88 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 60 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-10-07.
Other commands, from other repositories
pull-request
Full playbook: .claude/skills/pull-request/SKILL.md Monitoring commands: .claude/skills/pull-request/references/monitoring.md.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.