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 hamzabellouch/agent-skills --skill rabbitmq-message-queues-and-routinggit clone --depth 1 https://github.com/hamzabellouch/agent-skillsWrote 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/hamzabellouch/agent-skills/rabbitmq-message-queues-and-routing)<a href="https://agentmods.dev/skills/hamzabellouch/agent-skills/rabbitmq-message-queues-and-routing"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/rabbitmq-message-queues-and-routing/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/hamzabellouch/agent-skills/rabbitmq-message-queues-and-routing"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/rabbitmq-message-queues-and-routing.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.00082 | $0.02399 |
| Opus 5 | $0.00041 | $0.01200 |
| Sonnet 5 | $0.00016 | $0.00480 |
| Haiku 4.5 | $0.00008 | $0.00240 |
Grade A, and why
rabbitmq-message-queues-and-routing 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RabbitMQ Message Queues & Advanced Routing Guide
1. Overview & Topology Fundamentals
RabbitMQ is an enterprise message broker implementing the AMQP 0-9-1 protocol (alongside MQTT and STOMP support). Unlike log-centric event streams, RabbitMQ emphasizes smart broker / dumb consumer routing: producers publish messages to exchanges, which route messages into queues based on bindings and routing keys. Queues hold messages until consumers process and acknowledge them.
Key Architectural Axioms
- Decoupled Topology: Producers do not know which queues receive their messages; they publish solely to exchanges.
- Explicit Acknowledgments: Messages remain in queues until explicitly acknowledged by consumers (
basic.ack) or rejected/nacked (basic.nack/basic.reject). - Quorum Queues as Default: Legacy mirrored classic queues are deprecated. Production High Availability requires Quorum Queues backed by the Raft consensus algorithm.
2. Exchange Routing Strategies & Topologies
┌───────────────┐
│ Direct Exch │─── "orders.created" ───► [ Queue: Billing ]
└───────────────┘
│
▼
[ Producer ] ──────► ┌───────────────┐
│ Topic Exch │─── "orders.*" ───► [ Queue: Analytics ]
└───────────────┘
│
▼
┌───────────────┐
│ Fanout Exch │─── (Broadcast) ───► [ Queue: AuditLog ]
└───────────────┘
2.1 Exchange Matrix
| Exchange Type | Matching Logic | Common Use Case |
|---|---|---|
| Direct | Exact match between routing key and binding key (routing_key == binding_key) |
Targeted worker task queues, point-to-point command routing. |
| Fanout | Ignores routing key; broadcasts to all bound queues | System-wide notification fan-out, audit logging, cache invalidation. |
| Topic | Wildcard matching (* matches 1 word, # matches 0 or more words) |
Domain event hierarchies (e.g., europe.orders.created, *.orders.#). |
| Headers | Matches message header key-value pairs (x-match: all or any) |
Routing based on structured metadata (e.g., region, tenant_id, format). |
| Consistent-Hash | Hashes routing key or header to distribute messages across queues | Load balancing across multiple dedicated processing queues while maintaining hash key ordering. |
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.
- 9d ago First seen · 248 lines · 82 tokens per session scan A f3c800efcd24
rabbitmq-message-queues-and-routing is a skill published in the GitHub repository hamzabellouch/agent-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 82 tokens to every session and 2,399 once invoked, about $0.0004 per session on Opus 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-09-03.
Other skills, from other repositories
api-and-interface-design
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
ubiquitous-language
Maintain a project thesaurus (domain glossary) following DDD ubiquitous language principles. Use PROACTIVELY when naming anything: variables, functions, classes, modules, database fields, API endpoints, events, files, or directories. Also use when the user asks to "create thesaurus", "update glossary", "add term"…
laravel-expert
Laravel & PHP Development Instructions for GitHub Copilot.
nodejs-codestyle
Custom Instructions: Node.js Backend & Architecture Expert.
php-laravel-codestyle
Custom Instructions: PHP 8+ & Laravel Architecture Expert.
api-design
Design and implement REST APIs with consistent conventions, versioning, error contracts, and security.