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/fprochazka/claude-code-plugins/rabbitmqadminnpx skills add fprochazka/claude-code-plugins --skill rabbitmqadmingit clone --depth 1 https://github.com/fprochazka/claude-code-pluginsWhat 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.00063 | $0.01130 |
| Opus 5 | $0.00032 | $0.00565 |
| Sonnet 5 | $0.00013 | $0.00226 |
| Haiku 4.5 | $0.00006 | $0.00113 |
Grade A, and why
rabbitmqadmin 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 2d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
rabbitmqadmin
Command-line interface for RabbitMQ Management HTTP API (rabbitmqadmin-ng). Read-only inspection of vhosts, queues, exchanges, and bindings.
First Step: List Available Connections
Always start by listing configured connections:
rabbitmqadmin config_file show
This shows all configured RabbitMQ instances (passwords masked). Present the list to the user and ask which one to use. If the user's request already implies a specific connection, use it directly.
All commands below use <NODE> as a placeholder — replace it with the actual connection name from the config.
Virtual Hosts
After selecting a connection, list available vhosts to determine the --vhost value:
rabbitmqadmin --node <NODE> vhosts list
All commands below use <VHOST> as a placeholder — replace it with the actual vhost name from the list.
Queues
List Queues
rabbitmqadmin --node <NODE> queues list --vhost <VHOST>
Inspect a Queue
rabbitmqadmin --node <NODE> queues show --name <QUEUE> --vhost <VHOST>
Exchanges
rabbitmqadmin --node <NODE> exchanges list --vhost <VHOST>
Bindings
rabbitmqadmin --node <NODE> bindings list --vhost <VHOST>
Filtering and Output
The CLI has no built-in name filtering. To filter or limit output, use only these pipe targets — they are auto-approved by the permission hook:
| grep— filter lines by pattern (supports-i,-v,-E,-c, etc.)| head— show first N lines| tail— show last N lines> /path/to/fileor>> /path/to/file— redirect output to a file2>&1— redirect stderr to stdout
Do not use sort, wc, awk, sed, tee, or other commands in pipes — they will require manual approval. Prefer grep/head/tail for all filtering needs.
rabbitmqadmin --node <NODE> --vhost <VHOST> queues list | grep <PATTERN>
rabbitmqadmin --node <NODE> --vhost <VHOST> exchanges list | grep -i <PATTERN>
rabbitmqadmin --node <NODE> --vhost <VHOST> queues list | head -20
rabbitmqadmin --node <NODE> --vhost <VHOST> queues list | grep <PATTERN> | tail -5
rabbitmqadmin --node <NODE> --vhost <VHOST> queues list > /tmp/queues.txt
rabbitmqadmin --node <NODE> --vhost <VHOST> queues list 2>&1 | grep <PATTERN>
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.
- 2d ago First seen · 126 lines · 63 tokens per session scan A 8376aacdd820
rabbitmqadmin is a skill published in the GitHub repository fprochazka/claude-code-plugins (11 stars, last pushed 4d ago), licensed MIT. It adds 63 tokens to every session and 1,130 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…