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 commands/dvdsgl/claude-imessage/imessage-daemongit clone --depth 1 https://github.com/dvdsgl/claude-imessageWrote 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/commands/dvdsgl/claude-imessage/imessage-daemon)<a href="https://agentmods.dev/commands/dvdsgl/claude-imessage/imessage-daemon"><img src="https://agentmods.dev/badge/commands/dvdsgl/claude-imessage/imessage-daemon.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.00028 | $0.00799 |
| Opus 5 | $0.00014 | $0.00400 |
| Sonnet 5 | $0.00006 | $0.00160 |
| Haiku 4.5 | $0.00003 | $0.00080 |
Grade A, and why
imessage-daemon 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iMessage Daemon Management
Manage the iMessage auto-reply daemon that monitors incoming messages and responds autonomously.
User Request
The user wants to: {{command}}
Default to "status" if no command specified.
Available Commands
- start: Start the daemon (requires configuration)
- stop: Stop the running daemon
- status: Check if daemon is running and show logs
Your Task
-
Determine the command: Extract the action from the user's request (start|stop|status)
-
Locate the daemon script: The plugin installation includes the daemon at:
- Find plugin installation path (typically in Claude Code's plugin directory)
- Daemon script is at:
skills/imessage/daemon/imessage-auto-reply-daemon.sh
-
Execute the appropriate action:
For START:
- Check if environment variables are configured:
IMESSAGE_CONTACT_PHONE(required)IMESSAGE_CONTACT_NAME(required)IMESSAGE_CONTACT_EMAIL(optional)
- If not configured, guide user to set them:
export IMESSAGE_CONTACT_PHONE="4155551234" export IMESSAGE_CONTACT_NAME="John Doe" export IMESSAGE_CONTACT_EMAIL="[email protected]" # optional - Create tmp directory if needed:
mkdir -p ~/tmp/imessage - Start the daemon in background:
nohup /path/to/plugin/skills/imessage/daemon/imessage-auto-reply-daemon.sh > /dev/null 2>&1 & - Confirm it started and show the PID
- Show how to view logs
For STOP:
- Find the daemon process:
ps aux | grep imessage-auto-reply-daemon | grep -v grep - Kill it:
pkill -f imessage-auto-reply-daemon - Confirm it was stopped
- Show any final log messages
For STATUS:
- Check if daemon is running:
ps aux | grep imessage-auto-reply-daemon | grep -v grep - If running:
- Show PID and how long it's been running
- Show last 10 lines of daemon log:
tail -10 ~/tmp/imessage/imessage-auto-reply.log - Show last 10 lines of agent log:
tail -10 ~/tmp/imessage/imessage-agent.log - Show configuration (contact phone/name)
- If not running:
- Confirm it's not running
- Show how to start it with
/imessage-daemon start
- Check if environment variables are configured:
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.
- 5d ago First seen · 105 lines · 28 tokens per session scan A 428bbe785458
imessage-daemon is a command published in the GitHub repository dvdsgl/claude-imessage (54 stars, last pushed 9mo ago), licensed MIT. It adds 28 tokens to every session and 799 once invoked, about $0.0001 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.