Borrowing it
Nothing to install: this file belongs to advenimus/conduit-desktop. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/advenimus/conduit-desktop/main/.claude/skills/verify-sync/SKILL.mdgit clone --depth 1 https://github.com/advenimus/conduit-desktopWrote 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/advenimus/conduit-desktop/verify-sync)<a href="https://agentmods.dev/skills/advenimus/conduit-desktop/verify-sync"><img src="https://agentmods.dev/badge/skills/advenimus/conduit-desktop/verify-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/advenimus/conduit-desktop/verify-sync"><img src="https://agentmods.dev/badge/skills/advenimus/conduit-desktop/verify-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.00121 | $0.02872 |
| Opus 5.5 | $0.00048 | $0.01149 |
| Sonnet 5.5 | $0.00024 | $0.00574 |
| Haiku 4.5 | $0.00012 | $0.00287 |
Grade A, and why
verify-sync scanned grade A with 1 finding 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 12d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| appwrite phase fails or the API does not answer | Stack never set up, half-started, or short of memory | If the message names a missing `conduit-dev.env`, run `npm run appwrite:setup`. Check `curl -s http://localhost:8 How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/verify-sync: sync and device-limit suite
Runs npm run verify:sync (node scripts/verify/run.mjs sync). Real Electron devices share one
"cloud" folder, sign in as generated test users on a local Appwrite, and are driven like a user. The
spec under test is docs/MULTI_DEVICE_SYNC.md (sections 5, 6 and 7); the harness reference is
scripts/verify/README.md. Every suite at once is the verify skill; password changes, the vault
lifecycle, copies, backups and offline or team resilience are the verify-data skill.
What it proves
Each scenario uses its own devices (s1a, s1b, ...) and its own Vault.conduit.
| Scenario | In plain words |
|---|---|
free-takeover-server |
On Free, device B opens a vault A has open, is offered a take-over ("On the Free plan a vault can be open on one device at a time."), takes it and gets A's data; A is locked out and offered "Use here instead". |
take-back |
A presses "Use here instead" and gets the vault back; B is locked out. |
pro-merge-and-conflict |
On Pro both devices stay open. Edits to different fields merge with no conflict. The same field edited on both, and an edit against a delete, show up as conflicts; they are resolved in the review panel ("Keep item" for the delete) and both devices end the same. |
downgrade-and-upgrade |
Pro to Free with two devices open locks out exactly one (lease reason plan_limit, plan-limit message) while the other stays unlocked; back to Pro the locked-out device reopens with no take-over and the other is not disturbed. |
signout-releases-lease |
Signing out frees the device's server lease within seconds. |
signed-out-claims |
With nobody signed in (counts as Free), the owner claim inside the vault file still drives the take-over dialog and locks A out; B keeps the vault. |
legacy-writer |
An in-place edit by an old desktop build (0.17) is absorbed with no conflict and leaves no side files. |
file-safety |
Across the whole suite no -wal, -shm or -journal file appears in the cloud folder; every vault file has SQLite header bytes 18/19 = 2/2 (WAL) and opens the way iOS 1.0.5 opens it. Run alone it only covers its own vault, so judge it from a full suite run. |
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.
- 12d ago Changed · -2 lines · +11 tokens per session 93b4873c3292
- 28d ago First seen · 141 lines · 110 tokens per session scan A b5080aae3d52
verify-sync is a skill published in the GitHub repository advenimus/conduit-desktop (19 stars, last pushed yesterday), licensed Apache-2.0. It adds 121 tokens to every session and 2,872 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-01.
Other skills, from other repositories
winui-ui-testing
Write and run automated UI tests for Windows desktop apps (WinUI 3, WPF, WinForms, Win32) with the winapp ui harness: one batch script, assertions, input, file pickers, dialogs, screenshots, locally or in Windows Sandbox. Use when asked for UI tests or to verify a feature end to end.
Appium Mobile Testing
Mobile application testing skill using Appium for iOS and Android, covering device capabilities, selectors, gestures, and cross-platform testing strategies.
browser-qa
Use when validating or debugging a workflow in the embedded browser and you need a reproducible, evidence-first loop.
performance-engineer
Becomes a senior performance engineer who identifies bottlenecks, designs optimization strategies, and conducts load testing using systematic profiling and benchmarking methodology. Use when the user needs performance analysis, load testing, bottleneck identification, latency optimization, or capacity planning. Do NOT…
Desktop Application Testing
Testing desktop applications built with Electron, Tauri, or native frameworks including window management, IPC, tray icons, and auto-update testing.
playwright
Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via playwright-cli or the bundled wrapper script.