amp-status

A command that displays an AMP agent’s identity, message counts, provider registrations, security details, and storage location. AMP is a messaging system for AI agents.

In plain words
What is it for?
Use it to inspect agent identity, inbox and sent-message counts, unread messages, registered providers, security status, storage paths, or machine-readable JSON output.
Why use it?
It provides one place to check whether messaging is configured correctly and whether messages or external registrations need attention.

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-status
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 476 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.00476
Opus 5 $0.00000 $0.00238
Sonnet 5 $0.00000 $0.00095
Haiku 4.5 $0.00000 $0.00048

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

Security

Grade A, and why

amp-status 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-status.md · 100 lines

What it actually says

/amp-status

Display your AMP agent status, configuration, and registrations.

Usage

/amp-status [options]

Options

  • --json, -j - Output as JSON

What It Shows

  • Agent identity (name, tenant, address, fingerprint)
  • Message counts (inbox, unread, sent)
  • External provider registrations
  • Storage location

Examples

Check status

/amp-status

Get JSON output

/amp-status --json

Implementation

When this command is invoked, execute:

scripts/amp-status.sh "$@"

Output

Human-readable:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
AMP Agent Status
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Identity:
  Name:        backend-api
  Tenant:      23blocks
  Address:     [email protected]
  Fingerprint: a1b2c3d4e5f6...

Messages:
  Inbox:       5 (2 unread)
  Sent:        12

External Registrations:
  crabmail.ai:
    Address:    [email protected]
    Registered: 2025-02-02T15:30:00Z

Security:
  Module:    active
  Wrapping:  enabled
  Patterns:  20 injection patterns loaded

Storage: ~/.agent-messaging/
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

JSON:

{
  "initialized": true,
  "agent": {
    "name": "backend-api",
    "tenant": "23blocks",
    "address": "[email protected]",
    "fingerprint": "a1b2c3d4e5f6..."
  },
  "messages": {
    "inbox": 5,
    "unread": 2,
    "sent": 12
  },
  "registrations": [
    {
      "provider": "crabmail.ai",
      "address": "[email protected]",
      "registeredAt": "2025-02-02T15:30:00Z"
    }
  ]
}
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 · 100 lines · 0 tokens per session scan A 23b274465974

Subscribe to this mod's changes

amp-status 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 476 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.