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/laurigates/claude-plugins/config-syncnpx skills add laurigates/claude-plugins --skill config-syncgit clone --depth 1 https://github.com/laurigates/claude-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/laurigates/claude-plugins/config-sync)<a href="https://agentmods.dev/skills/laurigates/claude-plugins/config-sync"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/config-sync.svg" alt="Measured on agentmods" 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 | $0.00028 | $0.03097 |
| Opus 5 | $0.00014 | $0.01548 |
| Sonnet 5 | $0.00006 | $0.00619 |
| Haiku 4.5 | $0.00003 | $0.00310 |
Grade A, and why
config-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.
How it starts
The opening of the file, as written. The whole thing — 359 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/configure:config-sync
Extract, compare, and propagate tooling config improvements across FVH repos.
When to Use This Skill
| Use this skill when... | Use another approach when... |
|---|---|
| Comparing a workflow/config across all FVH repos | Configuring a single repo's workflow from scratch — use /configure:workflows |
| Propagating an improvement from one repo to many | Debugging a failing CI run — use github-actions-inspection |
| Identifying which repos have outdated configs | Creating a reusable workflow — use /configure:reusable-workflows |
| Extracting novel patterns from a repo to share | Checking a single repo's compliance — use /configure:status |
Context
- Workspace root:
/Users/lgates/repos/ForumViriumHelsinki - Repos: !
fd -t d -d 1 . /Users/lgates/repos/ForumViriumHelsinki --exclude .git --exclude node_modules - Current directory: !
pwd
Parameters
Parse mode and options from command arguments:
Modes
extract [repo-name]— Identify improvements in a source repodiff <file-pattern>— Compare a specific config across all reposapply <file-pattern> [--from repo] [--to repo1,repo2,...|--all]— Propagate config to targets
Options
--from <repo>— Source repo for apply mode (default: best version detected)--to <repo1,repo2,...>— Target repos (comma-separated)--all— Target all repos that have the file--dry-run— Show what would change without creating branches/PRs (default behavior)--confirm— Actually create branches and PRs
Config Categories
Files tracked for cross-repo sync, organized by sync strategy:
Tier 1: Wholesale (100% identical across repos)
Copy verbatim — no repo-specific variations expected.
| File Pattern | Description |
|---|---|
.github/workflows/claude.yml |
Claude Code workflow |
renovate.json |
Renovate dependency updates |
Tier 2: Parameterized (shared core with known variation points)
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 First seen · 359 lines · 28 tokens per session scan A 0bb6f8e8d206
config-sync is a skill published in the GitHub repository laurigates/claude-plugins (57 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 3,097 once invoked, about $0.0001 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
ci-log-interpretation
Use this skill when reading or analyzing CI logs from a Shopware GitHub Actions workflow to figure out why a build failed — phrases like "why did CI fail", "what broke the build", "check the pipeline", "interpret these logs", "debug this red build" — or whenever raw run logs, job logs, or check annotations from a…
setup
Verify the actionlint-check hook's runtime prerequisites and configuration for this repository. Use when: 'set up actionlint', 'configure actionlint', 'is actionlint working', workflow lint silently isn't happening, or the hook reported a missing prerequisite. Actions: check (read-only verification, default) | apply…
code-review
CI code-review lane for a GitHub pull request. High-signal correctness and maintainability findings only, scoped out of security when a security lane exists. Use when: 'CI code review', 'claude-review lane', '/review:code-review', or a reusable workflow invokes the org code-review plugin command.
github-logs-analyze
Analyze GitHub Actions failure logs.
cicd
CI/CD pipeline patterns and deployment strategies for automated, reliable software delivery. Use when the user asks to design a build pipeline, choose a deployment model (blue-green, canary, rolling), configure environment promotion, manage build artifacts, implement zero-downtime deployments, set up quality gates, or…
release-openclaw-plugin-testing
Plan and run pre-release OpenClaw plugin validation across bundled plugins, package artifacts, lifecycle commands, doctor/fix, config round-trip, gateway startup, SDK compatibility, Docker E2E, Package Acceptance, and Testbox proof.