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/derek-larson14/delegate/messagesgit clone --depth 1 https://github.com/derek-larson14/delegateWhat 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.00017 | $0.02409 |
| Opus 5 | $0.00009 | $0.01205 |
| Sonnet 5 | $0.00003 | $0.00482 |
| Haiku 4.5 | $0.00002 | $0.00241 |
Grade A, and why
messages 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 2d 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.
curl -sL https://raw.githubusercontent.com/derek-larson14/delegate/main/ops/scripts/beeper-cli.sh -o ./ops/scripts/beeper-cli.sh How it starts
The opening of the file, as written. The whole thing — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Beeper Messages Assistant
Access messages across all your chat platforms via Beeper Desktop API. Works with WhatsApp, Telegram, Signal, Instagram, LinkedIn, Discord, Slack, and more.
Setup (check in order)
Step 1: Check if already working
./ops/scripts/beeper-cli.sh status 2>&1
If shows ERROR: jq is required → Check if they have Homebrew:
which brew
If brew exists → run brew install jq yourself, then re-run status.
If no brew → tell user: "jq needs Homebrew. In Finder, open your workspace folder and double-click SETUP.command - it'll install Homebrew and the tools you need. Follow the prompts in the terminal window, then try /messages again."
If shows BEEPER_CONNECTED → Ready. If user just said "/messages" with no specific request, ask: "What can I help you find in your messages?"
If shows BEEPER_NOT_INSTALLED → Share the script's output with the user. It explains what Beeper is and how to install it.
If shows BEEPER_NOT_RUNNING → Tell the user:
"Beeper Desktop API needs to be enabled:
- Open Beeper Desktop
- Go to Settings → Developers
- Toggle ON 'Beeper Desktop API' at the top
- (Optional) Enable 'Start on launch' so it stays on
Let me know when that's done."
Then re-run the status check.
If shows BEEPER_UNAUTHORIZED or ERROR: No token configured → Tell the user:
"I need a token to access your messages:
- In Beeper Desktop: Settings → Developers
- Click '+' next to 'Approved connections'
- Copy the token it generates
- Paste it here and I'll save it for you"
When they paste the token, save it:
./ops/scripts/beeper-cli.sh setup <their_token>
Then re-run status to confirm it works.
If script not found → Download it first:
mkdir -p ./ops/scripts
curl -sL https://raw.githubusercontent.com/derek-larson14/delegate/main/ops/scripts/beeper-cli.sh -o ./ops/scripts/beeper-cli.sh
chmod +x ./ops/scripts/beeper-cli.sh
Commands
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.
- 2d ago First seen · 312 lines · 17 tokens per session scan A a189bfbbfb1a
messages is a command published in the GitHub repository derek-larson14/delegate (39 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 2,409 once invoked, about $0.0001 per session on Opus 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-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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.