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 commands/wyre-ai/msp-claude-plugins/queue-statusgit clone --depth 1 https://github.com/WYRE-AI/msp-claude-pluginsWrote 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/wyre-ai/msp-claude-plugins/queue-status)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/queue-status"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/queue-status.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 | $0.00011 | $0.00473 |
| Opus 5 | $0.00005 | $0.00236 |
| Sonnet 5 | $0.00002 | $0.00095 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
queue-status 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 3d 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.
What it actually says
Queue Status
A read-only staffing snapshot for one queue, or every queue the connected account can access if none is specified: who's logged in, and how many calls are active against it right now.
Prerequisites
- A 3CX PBX connected (directly or through Conduit's BYO connector) with a
valid, authenticated MCP session — see the
api-patternsskill - MCP tools available for listing queues, a queue's agents, and currently
active calls (see the
calls-queuesskill)
Steps
-
Resolve the queue(s) in scope
If a queue name or ID was given, use it directly. Otherwise, list queues the user can access/manage and cover all of them.
-
Pull staffing for each queue
List each queue's agents. Note which are logged in versus logged out — a queue can look adequately staffed by headcount while most agents are actually logged out.
-
Cross-reference active call load
List currently active calls and match them against the queue(s) in scope, where the tool's response makes that association available.
-
Report
For each queue: agent count, logged-in count, and active call count. Flag any queue with active calls but zero logged-in agents — that's the pattern that actually matters, not raw call volume.
Examples
/queue-status
/queue-status "Support"
/queue-status queue-42
Error Handling
- Queue not found: Re-list queues the user can access/manage — the requested name or ID may not match, or may belong to a queue this connection's account can't see.
- No active calls returned but the queue is known to be busy: Confirm
the MCP session hasn't gone stale (see
/pbx-health-check) before reporting the queue as idle.
Related Commands
/find-contact— resolve who a specific agent extension belongs to/pbx-health-check— broader PBX liveness check if queue data looks stale or missing
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.
- 3d ago First seen · 65 lines · 11 tokens per session scan A 23879f50c2db
queue-status is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (43 stars, last pushed 3d ago), licensed Apache-2.0. It adds 11 tokens to every session and 473 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 commands, from other repositories
research_codebase
Document codebase as-is with thoughts directory for historical context.
iterate_plan
Iterate on existing implementation plans with thorough research and updates.
create_handoff
Create handoff document for transferring work to another session.
speckit.verify-tasks
Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).
vibe-check
Audit a vibe-coded app across the six things that actually block shipping, and get a prioritized fix list.
statusline-install
Add the backlog badge (📋 N open items) to the Claude Code statusLine. Wraps an existing statusLine if you have one, creates it otherwise. Edits /.claude/settings.json (or $CLAUDECONFIGDIR).