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-specgit 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-spec)<a href="https://agentmods.dev/skills/avivsinai/agent-message-queue/amq-spec"><img src="https://agentmods.dev/badge/skills/avivsinai/agent-message-queue/amq-spec/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-spec"><img src="https://agentmods.dev/badge/skills/avivsinai/agent-message-queue/amq-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 128 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00040 | $0.01077 |
| Opus 5.5 | $0.00016 | $0.00431 |
| Sonnet 5.5 | $0.00008 | $0.00215 |
| Haiku 4.5 | $0.00004 | $0.00108 |
Grade A, and why
amq-spec 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-spec — 100% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AMQ collaborative specification
Two agents research a design problem independently, discuss it, and converge on one plan. The user approves the plan before anyone implements it.
Phases run in order:
Research -> Discuss -> Draft -> Review -> Present -> Execute
Per-phase commands and the research and plan templates are in the spec workflow.
Parse input
From the user prompt, extract:
- topic: short kebab-case spec name (e.g.,
auth-token-rotation) - partner: partner agent handle (default:
codex) - problem: the full design problem statement
If topic/problem are unclear, ask for clarification.
Pre-flight
- Verify AMQ is available:
which amq - Verify the AMQ root is discoverable (
.amqrc, AMQ env vars, or the default.agent-maillayout); otherwise run:amq coop init - Use thread name:
spec/<topic>
Kickoff
Send the problem to the partner first, then start your own research. Both agents then research in parallel. Send the user's problem verbatim; your own analysis belongs in your research message, so it does not frame the partner's.
amq send --to "<partner>" --kind question \
--labels workflow:spec,phase:request \
--thread "spec/<topic>" --subject "Spec: <topic>" --body "<problem>"
Labels
Every spec message uses an ordinary AMQ kind plus these labels on the
spec/<topic> thread:
| Phase | Kind | Labels |
|---|---|---|
| Problem statement | question |
workflow:spec,phase:request |
| Research findings | brainstorm |
workflow:spec,phase:research |
| Discussion | brainstorm |
workflow:spec,phase:discuss |
| Plan draft | review_request |
workflow:spec,phase:draft |
| Plan feedback | review_response |
workflow:spec,phase:review |
| Final decision | decision |
workflow:spec,phase:decision |
| Progress/ETA | status |
workflow:spec |
When you receive a spec message
| Label | Your action |
|---|---|
phase:request |
Do your own research first, then send findings as brainstorm + phase:research. |
phase:research |
If you have not sent your own research on this thread, research and send it before you read the partner's. Then read the thread and start discussion as brainstorm + phase:discuss. |
phase:discuss |
Reply with your analysis; continue until aligned. |
phase:draft |
Review the plan and send feedback as review_response + phase:review. Do not implement. |
phase:review |
Revise the plan if needed, or confirm alignment. |
phase:decision |
Stop. Do not implement; see the approval gate below. |
What ships with it
1 file 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 b987e3a9a35a
- yesterday Changed · -49 lines 271052a3aba6
- 2d ago Changed 8b9afd1c6b52
- 3d ago Changed e8461c0f0377
- 4d ago Changed 4e1feedb03f0
- 7d ago Changed f18e546c3538
- 11d ago Changed 4cb9679c84af
- 12d ago Changed 820a60ce84fb
- 13d ago Changed 0c2e20724374
- 14d ago First seen · 147 lines · 40 tokens per session scan A e779628b48f1
amq-spec is a skill published in the GitHub repository avivsinai/agent-message-queue (88 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 1,077 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
hunk-launch-video
Produces Hunk videos by driving the real TUI headlessly in a PTY, compositing captioned 1080p frames in Chromium, and encoding with ffmpeg. Use for feature demos, workflow explainers, announcements, launch videos, and full-release roundups.
gog-workspace
Use the gog CLI for Google Workspace tasks across Gmail, Calendar, Drive, Docs, Sheets, Contacts, and related services. Use when the user asks to check email, search Gmail, inspect calendar events, find Drive files, read Docs or Sheets, or manage Google Workspace data through gog.
apple-calendar
Read macOS Calendar events via the icalBuddy CLI and create events via AppleScript (osascript). Use to check the user's calendar, agenda, upcoming events, or add an event on macOS.
apple-reminders
Manage Apple Reminders via the remindctl CLI on macOS — list, add, complete, delete, manage lists.
octo-mail
OCTO Agent Mail operations for reading, searching, policy-aware sending, preparing drafts, and checking delivery status exclusively through octo-cli.
octo-messaging
Messaging domain — send/edit/sync messages, read receipts, message search (search/all/files/media/around/groups, in-channel or cross-channel), groups and threads (User Bot), and event polling. Covers App Bot DM-only constraints. Load after octo-shared.