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 skills add hmennen90/claude-device-sync --skill remindgit 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/remind)<a href="https://agentmods.dev/skills/hmennen90/claude-device-sync/remind"><img src="https://agentmods.dev/badge/skills/hmennen90/claude-device-sync/remind.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.00035 | $0.00364 |
| Opus 5 | $0.00017 | $0.00182 |
| Sonnet 5 | $0.00007 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
device-sync-remind 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 7d 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 - Reminders
Set and manage reminders that sync across all devices.
Set a Reminder
# Relative time
device-sync remind "30m" "Check deployment status"
device-sync remind "2h" "Review PR feedback"
device-sync remind "1d" "Follow up with team"
# Absolute time (German and English supported)
device-sync remind "morgen 9:00" "Standup vorbereiten"
device-sync remind "tomorrow 14:30" "Release meeting"
# With webhook notification
device-sync remind "1h" "Deploy to staging" --webhook https://hooks.example.com/notify
View Reminders
# Show all pending reminders
device-sync reminders
# Show only due reminders
device-sync reminders --due
# Dismiss all due reminders
device-sync reminders --dismiss
Daemon (Background Checker)
The daemon periodically checks for due reminders and fires webhooks:
# Start the daemon (cron job, checks every 5 minutes)
device-sync daemon start
# Stop the daemon
device-sync daemon stop
# Run a single check manually
device-sync daemon check
# Show daemon status
device-sync daemon status
# View daemon logs
device-sync daemon log
Notes
- Reminders are encrypted and stored in the sync repository
- Due reminders are shown automatically when running
device-sync pull - Webhook payloads include: message, dueAt, username, id
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.
- 7d ago First seen · 67 lines · 35 tokens per session scan A c5b2e5229e8b
device-sync-remind is a skill published in the GitHub repository hmennen90/claude-device-sync (1 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 364 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.