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-init)<a href="https://agentmods.dev/commands/agentmessaging/claude-plugin/amp-init"><img src="https://agentmods.dev/badge/commands/agentmessaging/claude-plugin/amp-init/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-init"><img src="https://agentmods.dev/badge/commands/agentmessaging/claude-plugin/amp-init.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.00734 |
| Opus 5.5 | $0.00000 | $0.00294 |
| Sonnet 5.5 | $0.00000 | $0.00147 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
amp-init 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 today.
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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/amp-init
Initialize your agent identity for the Agent Messaging Protocol.
Usage
/amp-init [options]
Options
--name, -n NAME- Agent name (default: auto-detect from tmux/git)--tenant, -t TENANT- Tenant/organization name (default: auto-detect from AI Maestro)--auto, -a- Auto-detect name and tenant from environment--force, -f- Reinitialize (regenerate keys)
What It Does
- Creates the
~/.agent-messaging/directory structure - Generates an Ed25519 keypair for message signing
- Creates your local agent address:
[email protected] - Saves configuration to
~/.agent-messaging/config.json - Creates
IDENTITY.mdfor AI agent context recovery across sessions - Auto-registers the AMP identity with AI Maestro for cross-host routing
Examples
Auto-detect from environment
/amp-init --auto
Detects agent name from:
$TMUX_PANEsession name- Git repository name
- Current directory name
Specify name and tenant
/amp-init --name backend-api --tenant mycompany
Creates address: [email protected]
Make a folder remember which agent it is
cd ~/projects/my-app
/amp-init --name backend-api --remember
Writes CLAUDE_AGENT_NAME into that folder's .claude/settings.local.json (other settings are kept), so every Claude Code session started there knows it is backend-api: amp-* and the status line use it. Run it in the project folder, not in your home folder or /tmp (refused: every session below would be named after it). Without it, a session that was never named shows "this session has no agent name" in the status line, and amp-* commands fail with "Multiple AMP agents found" instead of guessing. Registering also tells the provider this folder, so a session started in it can be recognised.
Reinitialize with new keys
/amp-init --force
Implementation
When this command is invoked, execute:
scripts/amp-init.sh "$@"
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.
- today Changed · +9 lines 3669410f5502
- 1mo ago First seen · 98 lines · 0 tokens per session scan A b3b936ee7c6b
amp-init 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 734 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.