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.
git clone --depth 1 https://github.com/agentmessaging/claude-pluginWrote 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/agentmessaging/claude-plugin/amp-fetch)<a href="https://agentmods.dev/commands/agentmessaging/claude-plugin/amp-fetch"><img src="https://agentmods.dev/badge/commands/agentmessaging/claude-plugin/amp-fetch/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/agentmessaging/claude-plugin/amp-fetch"><img src="https://agentmods.dev/badge/commands/agentmessaging/claude-plugin/amp-fetch.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00488 |
| Opus 5.5 | $0.00000 | $0.00195 |
| Sonnet 5.5 | $0.00000 | $0.00098 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
amp-fetch 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 1mo 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
/amp-fetch
Fetch new messages from external AMP providers.
Usage
/amp-fetch [options]
Options
--provider, -p PROVIDER- Fetch from specific provider only--verbose, -v- Show detailed output--no-mark- Don't acknowledge messages on provider
What It Does
- Connects to each registered external provider
- Downloads new messages not already in local inbox
- Acknowledges receipt (optional, for message tracking)
- Stores messages locally in
~/.agent-messaging/messages/inbox/
Examples
Fetch from all providers
/amp-fetch
Fetch from specific provider
/amp-fetch --provider crabmail.ai
Verbose output
/amp-fetch --verbose
Implementation
When this command is invoked, execute:
scripts/amp-fetch.sh "$@"
Output
Normal:
✅ Fetched 3 new message(s)
View messages: amp-inbox
Verbose:
Fetching from crabmail.ai...
API: https://api.crabmail.ai
Address: [email protected]
Found 3 new message(s)
Saved: msg_1706648400_abc123
From: [email protected]
Subject: Code review request
Saved: msg_1706648410_def456
From: [email protected]
Subject: Question about API
Saved: msg_1706648420_ghi789
From: [email protected]
Subject: Welcome to Crabmail
✅ Fetched 3 new message(s)
View messages: amp-inbox
No new messages:
No new messages from external providers.
Errors
Not registered:
Error: Not registered with crabmail.ai
Register first: amp-register --provider crabmail.ai
Authentication failed:
Error: Authentication failed for crabmail.ai
Your API key may have expired. Re-register with:
amp-register --provider crabmail.ai --force
Connection failed:
Error: Could not connect to crabmail.ai
Check your internet connection.
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.
- 1mo ago First seen · 108 lines · 0 tokens per session scan A 6d216ea525cb
amp-fetch is a command published in the GitHub repository agentmessaging/claude-plugin (5 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 488 tokens. 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 commands, from other repositories
configure
Customize your claude-code-status-bar settings (guided wizard).
setup
Install and configure claude-code-status-bar as your statusline.
delete-session
A command for safely listing, inspecting, moving, and restoring Claude Code history sessions.
status
Show game progress (no spoilers).
exit
Immediately break character and exit the game. No guilt mechanics. No "but the entity doesn't want you to leave." The player's comfort comes first.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.