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/statusnpx skills add hmennen90/claude-device-sync --skill statusgit 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/status)<a href="https://agentmods.dev/skills/hmennen90/claude-device-sync/status"><img src="https://agentmods.dev/badge/skills/hmennen90/claude-device-sync/status.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.1 | $0.00037 | $0.00246 |
| Opus 5 | $0.00018 | $0.00123 |
| Sonnet 5 | $0.00007 | $0.00049 |
| Haiku 4.5 | $0.00004 | $0.00025 |
Grade A, and why
device-sync-status 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.
What it actually says
Device Sync - Status & Configuration
Status
Show current sync configuration, registered devices, and connection status:
device-sync status
Hook Management
Hooks enable automatic push/pull on session start/end:
# Install auto-sync hooks
device-sync hooks install
# Remove hooks
device-sync hooks uninstall
# Show hook status
device-sync hooks status
Team Management
Add team members to share sessions and memory (team mode only):
# Add a team member
device-sync team add <username>
# Add with role
device-sync team add <username> --role owner
Troubleshooting
If sync is not working:
- Check status:
device-sync status - Verify hooks:
device-sync hooks status - Try manual pull:
device-sync pull - Ensure the Git repo is accessible: check SSH keys or tokens
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 First seen · 53 lines · 37 tokens per session scan A a0ffb6786efb
device-sync-status is a skill published in the GitHub repository hmennen90/claude-device-sync (1 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 246 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
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
collaboration-platform-administration
Administers the email, chat, meeting and file-sharing platform the organization runs on — tenant and domain configuration, mail authentication and routing, phishing and spam controls, shared mailboxes and distribution groups, external sharing and guest access, permission sprawl in file storage, and retention and legal…
onboarding-and-offboarding
Designs the joining and leaving experience — first-day readiness, ramp to productivity, knowledge capture, and clean exits. Use this to design or fix onboarding, shorten time to productivity, structure a leaver process, capture knowledge before someone leaves, or coordinate the access and asset steps around a joiner…
alive:system-cleanup
The world feels messy. Stale tasks, orphan folders, v2 remnants, unsaved sessions — entropy is accumulating and needs to be addressed before it compounds. Scans across all walnuts, then surfaces issues one at a time.
alive:world
The human doesn't know what to work on, or wants to see everything at once. They need the big picture — what's active, what's stale, what needs attention. Renders a live world view grouped by ALIVE domain, then routes to open, tidy, find, history, or map.
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.