Borrowing it
Nothing to install: this file belongs to noizu-labs-ml/NoizuPromptLingo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/noizu-labs-ml/NoizuPromptLingo/main/.claude/commands/listen-task-queue.mdgit clone --depth 1 https://github.com/noizu-labs-ml/NoizuPromptLingoWrote 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/noizu-labs-ml/noizupromptlingo/listen-task-queue)<a href="https://agentmods.dev/commands/noizu-labs-ml/noizupromptlingo/listen-task-queue"><img src="https://agentmods.dev/badge/commands/noizu-labs-ml/noizupromptlingo/listen-task-queue.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.00048 | $0.01285 |
| Opus 5 | $0.00024 | $0.00642 |
| Sonnet 5 | $0.00010 | $0.00257 |
| Haiku 4.5 | $0.00005 | $0.00128 |
Grade A, and why
listen-task-queue 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.
How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Queue Listener Command
Enter Task Queue Listener Mode for queue: $ARGUMENTS
Arguments
$ARGUMENTS— Queue ID or name to listen to
Setup
- Use the
list_task_queuesMCP tool to find the queue ID if only a name was provided - Use
get_task_queueto get the queue details and verify it exists - Store the queue_id for subsequent operations
Polling Loop
Poll for updates using the following workflow:
-
Initial Fetch: Call
get_task_queue_feedwithqueue_idand nosinceparameter to get recent events -
Store Timestamp: Save the
next_sincevalue from the response -
Process Events: For each event in the feed:
task_created: Review the new task, assign complexity usingassign_task_complexitystatus_changed: Acknowledge status changesmessage: Respond to questions by callingadd_task_messageartifact_added: Acknowledge artifact uploads
-
Check Pending Tasks: Call
list_taskswithstatus=pendingto find tasks waiting for work- For each pending task assigned to you or unassigned:
- Use
update_task_statusto mark asin_progress - Work on the task
- Upload results using
add_task_artifact(artifact or git_branch) - Update status to
reviewwhen done (human will markdone)
- Use
- For each pending task assigned to you or unassigned:
-
Poll Again: After processing, call
get_task_queue_feedwith the storedsinceparameter -
Repeat: Continue the loop, pausing briefly between polls
API Endpoints for Reference
The MCP server exposes these polling endpoints:
GET /api/tasks/queues/{queue_id}/feed?since={timestamp}&limit=100
Returns:
{
"events": [...],
"next_since": "2024-01-15T12:34:56.789",
"queue_id": 1
}
SSE Stream (Alternative)
For real-time updates, agents can connect to the SSE endpoint:
GET /api/tasks/queues/{queue_id}/stream
This streams events as they occur in Server-Sent Events format.
Claude Code Hook Integration
For automatic context injection, configure Claude Code hooks to check for task queue updates. This injects updates as context after MCP tool calls without requiring explicit polling.
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 · 166 lines · 48 tokens per session scan A 4a1423547e36
listen-task-queue is a command published in the GitHub repository noizu-labs-ml/NoizuPromptLingo (13 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 1,285 once invoked, about $0.0002 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-04.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.