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/hmennen90/claude-device-sync/syncnpx skills add hmennen90/claude-device-sync --skill syncgit clone --depth 1 https://github.com/hmennen90/claude-device-syncWrote 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/hmennen90/claude-device-sync/sync)<a href="https://agentmods.dev/skills/hmennen90/claude-device-sync/sync"><img src="https://agentmods.dev/badge/skills/hmennen90/claude-device-sync/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.00033 | $0.00352 |
| Opus 5 | $0.00016 | $0.00176 |
| Sonnet 5 | $0.00007 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
device-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 3d 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.
What it actually says
Device Sync - Push & Pull
Manage cross-device synchronization of Claude Code sessions and memory.
Push (Upload)
Push the current session and memory to the sync repository:
# Push everything (session + memory)
device-sync push
# Push only memory files
device-sync push --memory-only
# Push only the current session
device-sync push --session-only
Pull (Download)
Pull the latest state from the sync repository:
# Pull everything
device-sync pull
# Pull only memory files
device-sync pull --memory-only
Status
Check the current sync status, registered devices, and configuration:
device-sync status
Sessions
List all synced sessions across devices:
# List all sessions
device-sync sessions
# Filter by user (team mode)
device-sync sessions --user <username>
# Filter by project
device-sync sessions --project <path>
Purge
Delete old sessions to free space:
# Delete sessions older than 30 days (default)
device-sync purge
# Custom retention period
device-sync purge --days 7
# Preview what would be deleted
device-sync purge --dry-run
Notes
- Push/pull is automatic when hooks are installed (
device-sync hooks install) - Memory sync only affects the current project's memory directory
- Sessions are encrypted with ChaCha20-Poly1305 before being stored
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.
- 3d ago First seen · 82 lines · 33 tokens per session scan A 501dfc60bcf7
device-sync is a skill published in the GitHub repository hmennen90/claude-device-sync (1 stars, last pushed 4mo ago), licensed MIT. It adds 33 tokens to every session and 352 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
self-service-and-knowledge
Builds the help center, in-product guidance, and knowledge base that let customers resolve problems without contacting anyone — content, findability, maintenance, and deflection measurement. Use this to build or fix a help center, reduce support volume, write documentation for customers, improve findability, or decide…
agent-memory
3-tier markdown memory protocol (shared/agent/conversation) for cross-session knowledge. TRIGGER when: reading or writing agent memory files, choosing which memory tier an insight belongs in, or starting a task needing prior context. SKIP: vector recall (use semantic-memory-mcp); distilling conversations into…
memory
Unified memory CRUD: write/update/delete/query file-based markdown entries and sync to MCP semantic store. TRIGGER when: saving a new memory entry, updating or deleting an existing entry, querying stored memories, or deduplicating before write. SKIP: 3-tier agent memory (use agent-memory); in-task vector recall (use…
semantic-memory-mcp
Proactive use of semantic-memory MCP tools (semanticsearch, semanticrecall). TRIGGER when: an agent should search vector memory for prior insights mid-task. SKIP: file-based 3-tier memory (use agent-memory); storing a new memory (use semantic-memory-store).
distill
Knowledge distillation methodology: candidate extraction, confidence scoring, tier routing, conversation-scoped mode. TRIGGER when: running /learn or /distill, deciding if an insight is memory-worthy, or scoring a knowledge candidate. SKIP: ad-hoc memory reads/writes (use agent-memory); vector storage (use…
operate-hermes-agent
Install, update, migrate to, configure, run, secure, and troubleshoot Hermes Agent across its CLI, TUI, desktop, dashboard, profiles, tools, skills, memory, models, goals, voice, sessions, worktrees, and terminal backends.