amp-read

A command that opens one message from the agent’s inbox or sent folder. The inbox is the place where messages received by the agent are stored.

In plain words
What is it for?
Use it to read a message identified by its ID, inspect sent messages, or get message data in JSON format.
Why use it?
It lets you inspect a specific message without searching through the whole mailbox, while optionally leaving it unread.

Command

Install

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.

agentmods
npx agentmods add commands/agentmessaging/claude-plugin/amp-read
Clone the repo
git clone --depth 1 https://github.com/agentmessaging/claude-plugin
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 570 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00570
Opus 5 $0.00000 $0.00285
Sonnet 5 $0.00000 $0.00114
Haiku 4.5 $0.00000 $0.00057

Measured 2d ago against content hash eb725d0a0f65, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

amp-read 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 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.

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.

commands/amp-read.md · 106 lines

How it starts

The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/amp-read

Read a specific message from your inbox.

Usage

/amp-read <message-id> [options]

Arguments

  • message-id - The message ID (from amp-inbox)

Options

  • --no-mark-read, -n - Don't mark the message as read
  • --json, -j - Output raw JSON
  • --sent, -s - Read from sent folder instead of inbox

Examples

Read a message

/amp-read msg_1706648400_abc123

Read without marking as read

/amp-read msg_1706648400_abc123 --no-mark-read

Get JSON output

/amp-read msg_1706648400_abc123 --json

Read a sent message

/amp-read msg_1706648400_abc123 --sent

Implementation

When this command is invoked, execute:

scripts/amp-read.sh "$@"

Output

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
MESSAGE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

ID:       msg_1706648400_abc123
From:     [email protected]
To:       [email protected]
Subject:  Code review request
Date:     Feb 2, 2025 10:30 AM
Priority: high 🔴
Type:     request

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Please review PR #42 when you get a chance.
The OAuth implementation is ready for review.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CONTEXT
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
{
  "pr": 42,
  "repo": "agents-web"
}

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
ATTACHMENTS (2)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  ✅ att_1234_abc  report.pdf       (245.3 KB, application/pdf)
  ✅ att_1234_def  screenshot.png   (1.2 MB, image/png)

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✓ Marked as read

Actions:
  Reply:    amp-reply msg_1706648400_abc123 "Your reply message"
  Delete:   amp-delete msg_1706648400_abc123
  Download: amp-download msg_1706648400_abc123 --all

Message Not Found

If the message ID doesn't exist:

Error: Message not found: msg_invalid_id

Make sure the message ID is correct. Use 'amp-inbox' to list messages.

Read the full file on GitHub · 106 lines

Changes

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.

  1. 2d ago First seen · 106 lines · 0 tokens per session scan A eb725d0a0f65

Subscribe to this mod's changes

amp-read is a command published in the GitHub repository agentmessaging/claude-plugin (5 stars, last pushed 14d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 570 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.