taskrunner-list

A command that displays the current task queue, including whether each task is waiting, running, completed, or failed.

In plain words
What is it for?
Use it to inspect pending work, review task results, and identify when the taskrunner command should be run next.
Why use it?
It lets you see what work is queued before starting anything and makes an empty or blocked queue explicit.

Command

Install

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.

agentmods
npx agentmods add commands/stackbilt-dev/cc-taskrunner/taskrunner-list
Clone the repo
git clone --depth 1 https://github.com/Stackbilt-dev/cc-taskrunner
Per session 5 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 171 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00005 $0.00171
Opus 5 $0.00003 $0.00086
Sonnet 5 $0.00001 $0.00034
Haiku 4.5 $0.00001 $0.00017

Measured yesterday against content hash ba6c60fbc622, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

taskrunner-list 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 yesterday.

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.

plugin/commands/taskrunner-list.md · 27 lines

What it actually says

cc-taskrunner — List Queue

Show all tasks in the queue with their status.

Steps

  1. Run the list command:

    bash ${CLAUDE_PLUGIN_ROOT}/taskrunner.sh list
    
  2. If the queue file doesn't exist or is empty, tell the user and suggest /taskrunner-add.

  3. Present the results. Status symbols:

    • pending — waiting to run
    • running — currently executing
    • completed — finished successfully
    • failed — task errored or was blocked
  4. If there are pending tasks, suggest /taskrunner to execute them.

Changes

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.

  1. yesterday First seen · 27 lines · 5 tokens per session scan A ba6c60fbc622

Subscribe to this mod's changes

taskrunner-list is a command published in the GitHub repository Stackbilt-dev/cc-taskrunner (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 5 tokens to every session and 171 once invoked, about $0.0000 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-31.