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.
npx skills add dryvist/claude-code-plugins --skill sync-maingit clone --depth 1 https://github.com/dryvist/claude-code-pluginsWrote 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/skills/dryvist/claude-code-plugins/sync-main)<a href="https://agentmods.dev/skills/dryvist/claude-code-plugins/sync-main"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/sync-main/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/skills/dryvist/claude-code-plugins/sync-main"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/sync-main.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.00072 | $0.01226 |
| Opus 5.5 | $0.00029 | $0.00490 |
| Sonnet 5.5 | $0.00014 | $0.00245 |
| Haiku 4.5 | $0.00007 | $0.00123 |
Grade A, and why
sync-main 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 25d 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.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync Main
Update the local default branch from remote and merge it into the current working branch,
or all open PR branches when using the all parameter.
The skill keeps the name sync-main for continuity, but it syncs the repo's
actual default branch, not a literal main. On a trunk repo that is the same
thing; on a git-flow repo the default branch is develop, and this skill
treats develop as the sync target throughout.
Scope Parameter
| Usage | Scope |
|---|---|
/sync-main |
Current branch only |
/sync-main all |
All open PR branches |
CURRENT REPOSITORY ONLY - This command never crosses into other repositories.
Prerequisites
- You must be in a feature branch worktree (not on the default branch itself)
- The current branch should have no uncommitted changes
Resolve the Default Branch (Both Modes)
DEFAULT_BRANCH=$(gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name')
See /gh-cli-patterns (github-workflows) Canonical Default-Branch Detection for
what main vs develop implies. Use <DEFAULT_BRANCH> everywhere below.
Single Branch Mode (Default)
- Verify state:
git branch --show-current,git status --porcelain- STOP if on
<DEFAULT_BRANCH>or uncommitted changes
- STOP if on
- Sync default branch:
git fetch --all --prune --force && git pull(in the<DEFAULT_BRANCH>worktree) - Check for updates:
git fetch origin --force <DEFAULT_BRANCH> - Report: Show commits behind with
git log --oneline HEAD..origin/<DEFAULT_BRANCH>(informational only) - Merge:
git merge origin/<DEFAULT_BRANCH> --no-edit- If already up-to-date: skip to step 7 and report
- If merge succeeds cleanly: continue to step 6
- If conflicts occur: STOP, do not push. Report conflict status and follow the Conflict Resolution section below
- Push (only if merge succeeded cleanly):
git push origin $(git branch --show-current) - Report: branch,
<DEFAULT_BRANCH>SHA, merge status
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.
- 25d ago Changed f184f24d6763
- 1mo ago First seen · 110 lines · 72 tokens per session scan A f7251392ad86
sync-main is a skill published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 72 tokens to every session and 1,226 once invoked, about $0.0003 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.
Other skills, from other repositories
nav-pilot
Dispatch a Navigator task doc to Pilot as a labeled GitHub issue. Use when user says "dispatch TASK-XX to Pilot", "hand off to Pilot", "send to Pilot", or "queue for Pilot". One-way handoff (Navigator authors the spec, Pilot executes autonomously).
meta-feedback
A feedback reporter that collects bug reports and feature requests, then formats them as GitHub Issues. GitHub Issues are shared records used by development teams to track work and problems.
core-workflow
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, review-based validation, and communication standards.
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.
auto-claude
Autonomous multi-agent coding with git worktree isolation, QA validation, and memory. Use for complex features requiring autonomous implementation.
github-ops
GitHub remote operations and README authoring: repo creation, metadata, releases, issue/PR management with preview-before-send, README as a landing page (badge row, features-as-benefits, screenshots, Recent Updates), and read-only security auditing. Triggers on: write a README, improve the README, README badges…