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.
git clone --depth 1 https://github.com/secondsky/claude-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/commands/secondsky/claude-skills/queue-monitor)<a href="https://agentmods.dev/commands/secondsky/claude-skills/queue-monitor"><img src="https://agentmods.dev/badge/commands/secondsky/claude-skills/queue-monitor/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/commands/secondsky/claude-skills/queue-monitor"><img src="https://agentmods.dev/badge/commands/secondsky/claude-skills/queue-monitor.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.00017 | $0.02208 |
| Opus 5 | $0.00009 | $0.01104 |
| Sonnet 5 | $0.00003 | $0.00442 |
| Haiku 4.5 | $0.00002 | $0.00221 |
Grade A, and why
cloudflare-queues:monitor 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 7d 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 — 347 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Queue Monitor Command
Display real-time metrics and status for Cloudflare Queues.
Usage: /queue-monitor my-queue-name
Step 1: Validate Input
If queue name provided as argument ($1), use it. If not provided, list available queues:
wrangler queues list
Ask user to select from list or enter queue name manually.
Step 2: Fetch Queue Metrics
Run wrangler command to get current status:
wrangler queues info $queueName
Parse output to extract:
- Queue name
- Current backlog (messages waiting)
- Consumer count (active consumers)
- DLQ status (if configured)
- Last activity timestamp
Step 3: Display Formatted Metrics
Present metrics in organized, readable format:
═══════════════════════════════════════════════════════════
CLOUDFLARE QUEUES MONITOR
═══════════════════════════════════════════════════════════
Queue: order-processing-queue
Status: ✅ Active
Last Updated: 2025-12-27 10:30:45 UTC
───────────────────────────────────────────────────────────
QUEUE METRICS
───────────────────────────────────────────────────────────
Backlog: 125 messages
├─ Status: ⚠️ Moderate (>100)
├─ Trend: ↗ Growing (was 80, 5 min ago)
└─ Est. Clear Time: ~12 minutes (at current rate)
Consumer:
├─ Active: ✅ Yes (1 consumer)
├─ Batch Size: 10 messages
├─ Concurrency: 1
├─ Max Retries: 3
└─ Processing Rate: ~10 msg/min
Dead Letter Queue:
├─ Configured: ✅ Yes (order-processing-dlq)
├─ Failed Messages: 5 messages
└─ Status: ✅ Low (<10)
───────────────────────────────────────────────────────────
HEALTH INDICATORS
───────────────────────────────────────────────────────────
Overall Health: ⚠️ MODERATE
├─ Backlog: ⚠️ Moderate (125 messages)
├─ Consumer: ✅ Active
├─ DLQ: ✅ Low failure rate (<5%)
└─ Throughput: ⚠️ Below capacity (could process faster)
───────────────────────────────────────────────────────────
RECOMMENDATIONS
───────────────────────────────────────────────────────────
1. Consider increasing batch size to 25 for faster processing
→ Current: 10 | Recommended: 25 | Impact: 2.5x throughput
2. Review DLQ messages to identify failure patterns
→ 5 failures detected | Check: wrangler queues info order-processing-dlq
3. Monitor backlog trend over next 15 minutes
→ If continues growing, increase concurrency to 5
═══════════════════════════════════════════════════════════
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.
- 7d ago First seen · 347 lines · 17 tokens per session scan A acefeaff030a
cloudflare-queues:monitor is a command published in the GitHub repository secondsky/claude-skills (217 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 2,208 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-09-03.
Other commands, from other repositories
correlate
Find related failures through pattern matching.
diff
Compare two command outputs with intelligent diff.
open
Open/retrieve an offloaded output by ID or shortcut.
search
Search through offloaded outputs with hard caps.
stats
Show FewWord session statistics with rich output and token savings.
tag
Add tags to offloaded outputs for organization.