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.00736 |
| Opus 5.5 | $0.00027 | $0.00294 |
| Sonnet 5.5 | $0.00014 | $0.00147 |
| Haiku 4.5 | $0.00007 | $0.00074 |
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 6d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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 (0 no drift, 1 drift, 2 unverifiable) 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.
Spoke paths
The context/ files write this skill's directory as <skill-dir>, which is ${CLAUDE_SKILL_DIR}.
Put that path in place of the placeholder before running a command. Those files arrive through the
Read tool as plain bytes, so a ${…} token in them would reach the Bash tool unsubstituted, and the
Bash tool's environment has no CLAUDE_SKILL_DIR to expand it from. Basis: the plugins reference,
https://code.claude.com/docs/en/plugins/manifest-reference#where-each-variable-resolves, verified
2026-10-07; recheck when that table adds supporting files to where a ${…} reference resolves.
What ships with it
5 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.
- 6d ago Changed · +1 lines a89fd8e11472
- 17d ago Changed 768dbc3e1a30
- 23d ago Changed · +9 lines 4e2bdbbb7b7c
- 1mo ago Changed afefe5eceb8d
- 1mo ago Changed · -1 lines be0cc0d3e906
- 1mo ago Changed · -3 lines 27ca695f1fe6
- 1mo 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 (28 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 736 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-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.
git-operations
Git repository operations including branching, committing, pushing, and viewing history. Use for version control tasks. Destructive operations require explicit approval.
release
This skill should be used when the user wants to create a new release — bump version, tag, push, create GitHub release, and publish to npm through the release workflow. Use when user says "release", "bump version", "publish", "cut a release", or "release candidate".
css-coding-standards
CSS coding standards for systemprompt.io — one --sp- token system in OKLCH with color-mix derivation, BEM naming, one component per file, CSS-first behaviour, forbidden constructs, comment rules, and file limits. Canonical source of truth for all CSS. Load before writing or reviewing any stylesheet.
marketing-hypothesis-ledger
Append-only log of every marketing action taken and whether its hypothesis passed. Provides H-### ID allocation, in-flight queries for daily-marketing-brief, and maturation scoring for weekly-marketing-review. The spine of the hypothesis-driven marketing loop.