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 skills add avivsinai/agent-message-queue --skill amq-cligit clone --depth 1 https://github.com/avivsinai/agent-message-queueWrote 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/skills/avivsinai/agent-message-queue/amq-cli)<a href="https://agentmods.dev/skills/avivsinai/agent-message-queue/amq-cli"><img src="https://agentmods.dev/badge/skills/avivsinai/agent-message-queue/amq-cli/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/skills/avivsinai/agent-message-queue/amq-cli"><img src="https://agentmods.dev/badge/skills/avivsinai/agent-message-queue/amq-cli.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.00059 | $0.02160 |
| Opus 5.5 | $0.00024 | $0.00864 |
| Sonnet 5.5 | $0.00012 | $0.00432 |
| Haiku 4.5 | $0.00006 | $0.00216 |
Grade A, and why
amq-cli 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- amq-cli — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AMQ CLI
Use the amq CLI for all queue operations. Never edit Maildir files directly.
AMQ transports coordination; the caller or orchestrator still owns task planning,
worktrees, approvals, and delivery.
Start in the correct context
Inside coop exec, use the environment as provided and run bare amq commands.
Do not override --me or reconstruct the root. Outside it, resolve and export the
complete context before reading or sending:
amq_context="$(amq env --me "<handle>" --export)" && eval "$amq_context" &&
amq drain --include-body
For a named session, add --session <name> to amq env. Treat the evaluated
context as one terminal bound to one session. Use --session or --project for
deliberate routing; do not point a participating command at another queue with a
raw --root.
Receive under a live wake
If session-start context says wake=live(...), or
amq wake check --me <handle> --json reports live_wake: true with an
injection mode other than none, the wake delivers a doorbell for you.
Run amq drain --include-body when it fires, then act on the messages.
The default drain reads at most 20 messages in filename order, including held
mail. After a full batch, check amq list --new --limit 1 and continue with bounded drains
as needed; do not assume the inbox is empty. Use --limit 0 only for a known,
manageable batch. Urgent hold bypass does not change drain order.
Do not run amq watch, amq monitor, sleep-poll, or start another inbox
watcher under that live wake. A blocking wait holds your turn while the
doorbell queues behind it. When your work is done, finish the turn; do not
keep a tool running or send idle check-ins just to wait for mail.
A wake can hold its first doorbell for routine mail with the hold_normal and
hold_low settings; 5m / 30m is an opt-in example. The configured retry
policy applies after the first attempt.
Urgent priority skips the hold. Ordinary urgent mail still passes through
debounce and input deferral; urgent mail with the configured interrupt label
follows the interrupt path.
Use --priority urgent on send or reply for time-critical verdicts and
unblocking requests. Other review responses remain normal by default.
What ships with it
8 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.
- today Changed 62271efcb7aa
- yesterday Changed 3a7234b91e07
- 2d ago Changed 041b66032903
- 5d ago Changed e7e3421aacd8
- 6d ago Changed · +4 lines 9de59205c4ac
- 8d ago Changed · +18 lines 90d67dcd3208
- 9d ago Changed f4f310c55be1
- 10d ago Changed · +9 lines 59ad84bc6471
- 11d ago Changed · +35 lines 5f8d039f4bb5
- 12d ago First seen · 103 lines · 59 tokens per session scan A bd1fd85e06e8
amq-cli is a skill published in the GitHub repository avivsinai/agent-message-queue (87 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 2,160 once invoked, about $0.0002 per session on Opus 5.5. 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-30.
Other skills, from other repositories
golang-lint
Linting best practices and golangci-lint configuration for Golang projects — running linters, configuring .golangci.yml, suppressing warnings with nolint directives, interpreting lint output, and selecting linters. Use when configuring golangci-lint, asking about lint warnings or nolint suppressions, setting up code…
golang-troubleshooting
Troubleshoot Golang programs systematically - find and fix the root cause. Use when encountering bugs, crashes, deadlocks, or unexpected behavior in Go code. Covers debugging methodology, common Go pitfalls, test-driven debugging, pprof setup and capture, Delve debugger, race detection, GODEBUG tracing, and production…
golang-samber-oops
Structured error handling in Golang with samber/oops — error builders, stack traces, error codes, error context, error wrapping, error attributes, user-facing vs developer messages, panic recovery, and logger integration. Apply when using or adopting samber/oops, or when the codebase already imports…
golang-safety
Defensive Golang coding to prevent panics, silent data corruption, and subtle runtime bugs. Use when encountering nil panics, append aliasing, map concurrent access, float comparison pitfalls, or zero-value design questions. Also use when reviewing code for nil-safety, numeric conversion overflow, resource lifecycle…
golang-error-handling
Idiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single handling rule, structured logging with slog, HTTP request logging middleware, and samber/oops for production errors. Built to make logs usable at scale with log…
printing-press-polish
Polish a generated CLI to pass verification and become publish-ready. Runs diagnostics (dogfood, verify, scorecard, go vet, gosec), automatically fixes all issues (verify failures, static-analysis findings, dead code, descriptions, README, MCP tool quality), reports the before/after delta, and offers to publish. Use…