Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add melodic-software/claude-code-plugins/plugin install dometrainWrote 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/melodic-software/claude-code-plugins/sync)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/sync"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/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/skills/melodic-software/claude-code-plugins/sync"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/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.00068 | $0.00570 |
| Opus 5 | $0.00034 | $0.00285 |
| Sonnet 5 | $0.00014 | $0.00114 |
| Haiku 4.5 | $0.00007 | $0.00057 |
Grade A, and why
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 today.
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
Purpose
Report-only drift check between this plugin's vendored dometrain-grounding baseline
(vendor/SKILL.md) and Dometrain's current upstream skill content
(github.com/Dometrain/mcp, skills/dometrain-grounding/SKILL.md). There is one upstream
dependency and no CLI to upgrade, only vendored prose to diff.
Consumer vs maintainer role split: this skill is disable-model-invocation: true, so it is
reachable only by a human's explicit /dometrain:sync invocation, never by the model on its own
initiative. check (the only action) is report-only. The --refresh-baseline flag is not
skill-exposed; context/update.md documents it for a maintainer to type as a raw bash command in a
working clone.
check (report-only, the only action)
Run:
bash "${CLAUDE_PLUGIN_ROOT}/skills/sync/scripts/update.sh"
The script:
- Fetches Dometrain's current
skills/dometrain-grounding/SKILL.mdfromraw.githubusercontent.com. - Diffs it against
vendor/SKILL.md(stripping the vendored file's own attribution comment first, since upstream never carries it). - Reports "No drift detected" or shows the diff for manual review.
Never writes to vendor/SKILL.md or grounding/SKILL.md. Direct the user to
context/update.md for the maintainer-only integration protocol.
Output
Report the script's exit code and its stdout verbatim (or a short summary if long): drift
present or absent, and when present, point to context/update.md for the next step.
Boundaries
- Never model-invocable. This skill exists so a maintainer can check drift explicitly, not so the model can decide on its own that a check is warranted.
- Never runs
--refresh-baseline. That overwrites the vendor snapshot and is restricted to a maintainer typing the raw command directly in a working clone. - Never edits
grounding/SKILL.md. Integration is a human decision, documented incontext/update.md.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed · -1 lines be0cc0d3e906
- 2d ago Changed · -3 lines 27ca695f1fe6
- 5d ago First seen · 56 lines · 68 tokens per session scan A 46b0f60cebaa
sync is a skill published in the GitHub repository melodic-software/claude-code-plugins (15 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 570 once invoked, about $0.0003 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.
Other skills, from other repositories
parallel-orchestrator
Manage parallel Claude Code workstreams using git worktrees. Use when: splitting large tasks across multiple workers, coordinating parallel development, monitoring worker progress, integrating completed work, analyzing work item documents (code reviews, issue lists). Triggers: parallel, orchestrator, worktrees…
parallel-worker
Execute focused implementation tasks in a parallel workflow. Use when: working on assigned files in a worktree, making checkpoint commits, signaling dependencies or blockers, completing orchestrator-assigned tasks. Triggers: worker, checkpoint, worktree, assigned scope, commit prefix, parallel task.
auto-claude
Autonomous multi-agent coding with git worktree isolation, QA validation, and memory. Use for complex features requiring autonomous implementation.
changelog-summarizing
Use this skill when the user asks to summarize, recap, or post about repository changes in the Shopware AI Coding Tools marketplace since a given date — phrases like "write a changelog post for Discord", "recap this week's commits for Slack", "summarize what shipped since 2026-04-01", "draft a release announcement".…
issue-analyzing
Use this skill when the user asks to analyze a specific GitHub issue, understand what area of code an issue affects, assess an issue's scope, or research the code context around an issue — example triggers like "analyze issue.
release-info-writing
Use this skill when the user is completing features, deprecations, or breaking changes in the Shopware core repository that affect external developers, or when they ask to write release info, upgrade entries, release notes, release documentation, or changelog entries — phrases like "write a release info entry for my…