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-data/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-data)<a href="https://agentmods.dev/skills/advenimus/conduit-desktop/verify-data"><img src="https://agentmods.dev/badge/skills/advenimus/conduit-desktop/verify-data/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-data"><img src="https://agentmods.dev/badge/skills/advenimus/conduit-desktop/verify-data.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.00157 | $0.06429 |
| Opus 5.5 | $0.00063 | $0.02572 |
| Sonnet 5.5 | $0.00031 | $0.01286 |
| Haiku 4.5 | $0.00016 | $0.00643 |
Grade A, and why
verify-data 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/verify-data: vault data suites
Runs npm run verify:data (node scripts/verify/run.mjs backup copies lifecycle password resilience).
Real Electron devices share the run's "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; the harness
reference is scripts/verify/README.md. Every suite at once is the verify skill; the sync engine's
core loop (take-over, merge, conflicts, plan changes) is the verify-sync skill.
Pick the suite that covers what you changed and run it alone. Run all five only when your change spans several of them or the user asks for it:
| Suite | Run it alone | About | Covers |
|---|---|---|---|
password |
node scripts/verify/run.mjs password |
1 min | Master-password change on a synced vault (4.7, 4.8): the "Syncing paused" prompt, old and new passwords, erasing Recently deleted with the change. |
lifecycle |
node scripts/verify/run.mjs lifecycle |
3 min | Recently deleted and "Delete permanently" (4.7), rename and the other device's rebind (5.9), separate vault, damaged working copy, idle auto-lock, Settings > Sync. |
copies |
node scripts/verify/run.mjs copies |
2 min | Cloud conflict copies, user copies, older-desktop side files, mass-change snapshot and undo, two devices on two copies (5.5, 5.8, 5.10). |
backup |
node scripts/verify/run.mjs backup |
2 min | Local backup, rollback and restore as a new vault, cloud backup plan gate and downgrade (5.10, 8.1, 8.2). |
startup |
node scripts/verify/run.mjs startup |
3.5 min | Startup vault and automatic unlock (docs/AUTO_UNLOCK.md 8.2): the saved unlock across a relaunch, Lock and the screen lock keep asking, the escape hatch, Go to Vault Hub, a stale saved password, no automatic take-over, a missing file, sign-out and account switch forget it, the MCP hold, a team startup vault. Not part of verify:data. |
resilience |
node scripts/verify/run.mjs resilience |
2.5 min | Offline open and reconnect, a take-over learned on reconnect, the cached Pro tier, team vaults beside personal sync, export and import (4.2, 6.5 to 6.8). |
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 · -1 lines d79936357f23
- 28d ago First seen · 226 lines · 157 tokens per session scan A c6aa186aa6ea
verify-data is a skill published in the GitHub repository advenimus/conduit-desktop (19 stars, last pushed yesterday), licensed Apache-2.0. It adds 157 tokens to every session and 6,429 once invoked, about $0.0006 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.