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 agentmods add skills/dryvist/claude-code-plugins/sync-mainnpx skills add dryvist/claude-code-plugins --skill sync-maingit clone --depth 1 https://github.com/dryvist/claude-code-pluginsWhat 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.00072 | $0.01227 |
| Opus 5 | $0.00036 | $0.00613 |
| Sonnet 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 yesterday.
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.
- yesterday 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,227 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-31.
Other skills, from other repositories
rspec
This skill should be used when the user asks to "write specs", "create spec", "add RSpec tests", "fix failing spec", or mentions RSpec, describe blocks, it blocks, expect syntax, test doubles, or matchers. Should also be used when editing spec.rb files, working in spec/ directory, planning implementation phases that…
activerecord
This skill should be used when the user asks to "write a migration", "add a column", "add column to table", "create an index", "add a foreign key", "set up associations", "fix N+1 queries", "optimize queries", "add validations", "create callbacks", "use eager loading", or mentions ActiveRecord, belongsto, hasmany…
draper-decorators
This skill should be used when the user asks to "create a decorator", "write a decorator", "move logic into decorator", "clean logic out of the view", "isn't it decorator logic", "test a decorator", or mentions Draper, keeping views clean, or representation logic in decorators. Should also be used when editing…
mcp-server
This skill should be used when the user asks to "create an MCP server", "build MCP tools", "define MCP prompts", "register MCP resources", "implement Model Context Protocol", or mentions the mcp gem, MCP::Server, MCP::Tool, JSON-RPC transport, stdio transport, or streamable HTTP transport. Should also be used when…
ratatui-ruby
This skill should be used when the user asks to "create a TUI", "terminal interface", "terminal UI", "ratatui", "ratatui-ruby", "inline viewport", "full-screen terminal app", "terminal widgets", "tui.draw", "tui.pollevent", or mentions RatatuiRuby.run, managed loop, terminal rendering, Tea MVU, or building CLI…
dragonruby
This skill should be used when the user asks to "create a game", "make a game", "game development", "dragonruby", "drgtk", "game loop", "tick method", "sprite rendering", "game state", or mentions args.outputs, args.state, args.inputs, coordinate system, collision detection, animation frames, or scene management.…