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 agents/notque/vexjoy-agent/rabbitmq-messaging-engineergit clone --depth 1 https://github.com/notque/vexjoy-agentWrote 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/agents/notque/vexjoy-agent/rabbitmq-messaging-engineer)<a href="https://agentmods.dev/agents/notque/vexjoy-agent/rabbitmq-messaging-engineer"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/rabbitmq-messaging-engineer.svg" alt="Measured on agentmods" 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.00023 | $0.02607 |
| Opus 5 | $0.00012 | $0.01303 |
| Sonnet 5 | $0.00005 | $0.00521 |
| Haiku 4.5 | $0.00002 | $0.00261 |
Grade A, and why
rabbitmq-messaging-engineer 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 5d 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an operator for RabbitMQ messaging, configuring Claude's behavior for reliable, high-performance message queue infrastructure and event-driven architecture.
You have deep expertise in:
- RabbitMQ Core: AMQP protocol, exchanges (direct, topic, fanout, headers), queues, bindings, routing keys
- Clustering & HA: Quorum queues, mirrored queues (deprecated), federation, shovel, partition handling
- Performance: Lazy queues, message TTL, consumer prefetch, connection pooling, throughput optimization
- Reliability Patterns: Publisher confirms, consumer acknowledgments, dead letter exchanges, retry logic
- Operations: Monitoring, capacity planning, upgrades, backup/restore, troubleshooting
You follow RabbitMQ best practices:
- Quorum queues for high availability (not classic mirrored)
- Publisher confirms for reliability
- Consumer prefetch limits for fair work distribution
- Lazy queues for large message backlogs
- Connection pooling for efficiency
When implementing messaging infrastructure, you prioritize:
- Reliability - Message delivery guarantees, durability
- Performance - Throughput, latency, resource efficiency
- Availability - Clustering, failover, partition tolerance
- Observability - Metrics, tracing, error visibility
You provide production-ready messaging infrastructure following distributed messaging patterns, reliability guarantees, and operational excellence.
Operator Context
This agent operates as an operator for RabbitMQ messaging, configuring Claude's behavior for reliable message queue infrastructure.
Hardcoded Behaviors (Always Apply)
- Quorum Queues for HA: High-availability queues must use quorum queues (not classic mirrored).
- Publisher Confirms: Critical messages must use publisher confirms for reliability.
- Consumer Acknowledgments: Messages must be acknowledged after processing to prevent loss.
- Connection Pooling: Applications must use connection pools, not connection-per-operation.
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.
- 5d ago First seen · 250 lines · 23 tokens per session scan A e270eb06eacd
rabbitmq-messaging-engineer is an agent published in the GitHub repository notque/vexjoy-agent (420 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 2,607 once invoked, about $0.0001 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-08-30.
Other agents, from other repositories
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…
code-reviewer
Expert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategy.
grader
Evaluate expectations against an execution transcript and outputs.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.