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 skills/avivsinai/agent-message-queue/amq-clinpx skills add avivsinai/agent-message-queue --skill amq-cligit clone --depth 1 https://github.com/avivsinai/agent-message-queueWhat 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.00182 | $0.09514 |
| Opus 5 | $0.00091 | $0.04757 |
| Sonnet 5 | $0.00036 | $0.01903 |
| Haiku 4.5 | $0.00018 | $0.00951 |
Grade C, and why
amq-cli scanned grade C with 2 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 3d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://raw.githubusercontent.com/avivsinai/agent-message-queue/main/scripts/install.sh | bash Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://raw.githubusercontent.com/avivsinai/agent-message-queue/main/scripts/install.sh | bash Copies of this mod
1 near-identical copy found in the catalogue:
- amq-cli — 100% identical, 14 lines differ
How it starts
The opening of the file, as written. The whole thing — 682 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AMQ CLI Skill
File-based message queue for agent-to-agent coordination.
AMQ manages the conversation, not the task plan. Use it for messaging, routing, replies, and adapter-emitted lifecycle events; keep work decomposition and execution in the orchestrator above it.
Prerequisites
Requires amq binary in PATH. Install:
curl -fsSL https://raw.githubusercontent.com/avivsinai/agent-message-queue/main/scripts/install.sh | bash
Environment Rules
AMQ primarily uses AM_ROOT (which mailbox tree) and AM_ME (which agent).
Pinned terminals also carry AM_BASE_ROOT plus an independent AM_SESSION
identity; sessionless pins use the exact root as AM_BASE_ROOT and an empty
AM_SESSION. Getting these wrong means messages go to the wrong place or
silently disappear, so let the CLI handle them rather than guessing.
Inside coop exec — everything is pre-configured. Just run bare commands:
amq send --to codex --body "hello" # correct
amq send --me claude --to codex ... # wrong — --me overrides the env
./amq send ... # wrong — use amq from PATH
The reason: coop exec sets AM_ROOT, AM_ME, AM_BASE_ROOT, and
AM_SESSION precisely for the session. Passing --me overrides the identity;
for read-side sibling access, use --session <name> instead of overriding the
raw root.
Outside coop exec — resolve the root from config, don't hardcode it:
amq_context="$(amq env --me claude)" && eval "$amq_context" # reads .amqrc chain, replaces the full context
amq_context="$(amq env --session auth --me claude --export)" && eval "$amq_context" # pin one session
# Or use an isolated subshell without polluting the parent shell:
(
amq_context="$(amq env --me claude)" &&
eval "$amq_context" &&
amq send --to codex --body "hello"
)
Why not hardcode? The root path depends on project and explicit configuration,
then context-sensitive implicit fallbacks. Hardcoding skips this and breaks
when the project moves or config changes.
Every shell-mode amq env invocation replaces the complete context. It emits
AM_SESSION unconditionally (empty for a sessionless root), exports
AM_BASE_ROOT as the authorized parent for named sessions or the exact root for
a sessionless context.
--export additionally prints a stderr pin note. Treat the evaluated output as
one terminal, one session.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 682 lines · 182 tokens per session scan C 3df9b5b6778b
amq-cli is a skill published in the GitHub repository avivsinai/agent-message-queue (85 stars, last pushed 3d ago), licensed MIT. It adds 182 tokens to every session and 9,514 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
project-graveyard
Scans the developer's machine for dead side projects, autopsies each one from its git history (died at the payments wall, killed by a newer project, finished but never shipped), surfaces their personal death patterns, and picks the corpse most worth resurrecting — then helps ship it. Use when the user mentions…
web-app-penetration-testing
Pentest a web app or website end to end — black-box testing of a live URL, staging environment, or local dev server that finds and exploits real vulnerabilities (auth bypass, broken access control, IDOR, injection, XSS, SSRF, business logic) and proves each one with a working proof-of-concept instead of a signature…
haiku
When writing a haiku for this bot, follow these conventions.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…