queue-task

A helper for creating Claude Queue tasks when a Claude usage limit is near or substantial work remains. Claude Queue runs queued tasks later without requiring the current session to stay active.

In plain words
What is it for?
Use it to turn remaining coding or multi-step work into queued tasks, set their working directory and priority, and continue the work unattended.
Why use it?
It reduces the risk of unfinished work stopping when the available Claude quota runs out.

Skill for Claude CodeCodex

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 skills/vasiliyk/claude-queue/queue-task
Any agent
npx skills add vasiliyk/claude-queue --skill queue-task
Clone the repo
git clone --depth 1 https://github.com/vasiliyk/claude-queue

Made for: Claude Code, Codex.

Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,366 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.00057 $0.01366
Opus 5 $0.00028 $0.00683
Sonnet 5 $0.00011 $0.00273
Haiku 4.5 $0.00006 $0.00137

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

Security

Grade A, and why

queue-task 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.

skills/queue-task/SKILL.md · 167 lines

How it starts

The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Claude Queue Task Creator

This skill helps users quickly create tasks for claude-queue when approaching Claude Plan usage limits. It enables users to queue remaining work and walk away while tasks run unattended.

When to Use This Skill

Proactively suggest creating tasks when:

  • Multiple large code changes have been made in the session
  • Long conversation with many tool uses
  • User mentions they have more work to do
  • Complex refactoring or multi-step task is in progress
  • User explicitly says: "queue this", "create tasks", "I'm hitting limits"

Don't wait for user to hit limits - be proactive and help them avoid interruption.

Proactive Suggestion Template

When you notice significant work has been done, say:

"We've made good progress, but we're likely approaching your usage limits. Would you like me to create tasks for the remaining work? That way you can queue it up and let it run unattended."

List what tasks you could create and ask for confirmation.

Task Creation Approach

For Single Tasks

Provide a CLI command:

./claude-queue.py add "Task description" \
  --working-dir ~/path/to/project \
  --priority 10

For Multiple Tasks or Dependencies

Use the Write tool to create a YAML file directly in the project directory. Don't provide copy-paste commands - create the file immediately.

Task File Format

tasks:
  - prompt: "Clear, specific task description"
    session: "task-session-name"
    working_dir: "~/path/to/project"
    priority: 10
    max_attempts: 3
    depends_on: ["other-session-name"]  # optional

Priority Guidelines

  • Critical/Blockers: 15-20
  • High priority: 10-14
  • Normal: 5-9
  • Low priority: 1-4
  • Nice to have: 0

Task Description Best Practices

Good descriptions:

  • Clear and specific: "Refactor auth module to use OAuth2, update all endpoints"
  • Include acceptance criteria: "Add error handling and write tests for edge cases"
  • Self-contained: "Fix bug in user registration - email validation not working for +addresses"

Read the full file on GitHub · 167 lines

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 · 167 lines · 57 tokens per session scan A 120f62f8c803

Subscribe to this mod's changes

queue-task is a skill published in the GitHub repository vasiliyk/claude-queue (23 stars, last pushed 4mo ago), licensed MIT. It adds 57 tokens to every session and 1,366 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.

Related

Other skills, from other repositories

implementing-api-gateway-security-controls

Implements security controls at the API gateway layer including authentication enforcement, rate limiting, request validation, IP allowlisting, TLS termination, and threat protection. The engineer configures API gateways (Kong, AWS API Gateway, Azure APIM, Apigee) to act as a centralized security enforcement point…

xalgorix/xalgorix · 106 tokens

implementing-api-rate-limiting-and-throttling

Implements API rate limiting and throttling controls using token bucket, sliding window, and fixed window algorithms to protect against brute force attacks, credential stuffing, resource exhaustion, and API abuse. The engineer configures per-user, per-IP, and per-endpoint rate limits using Redis-backed counters, API…

xalgorix/xalgorix · 114 tokens

performing-api-rate-limiting-bypass

Tests API rate limiting implementations for bypass vulnerabilities by manipulating request headers, IP addresses, HTTP methods, API versions, and encoding schemes to circumvent request throttling controls. The tester identifies rate limit headers, determines enforcement mechanisms, and attempts bypasses including…

xalgorix/xalgorix · 118 tokens

detecting-api-enumeration-attacks

Detect and prevent API enumeration attacks including BOLA and IDOR exploitation by monitoring sequential identifier access patterns and authorization failures.

xalgorix/xalgorix · 32 tokens

implementing-api-abuse-detection-with-rate-limiting

Implement API abuse detection using token bucket, sliding window, and adaptive rate limiting algorithms to prevent DDoS, brute force, and credential stuffing attacks.

xalgorix/xalgorix · 43 tokens

API Gateway Testing

API gateway testing skill covering rate limiting validation, request routing, authentication proxy testing, load balancing verification, circuit breaker testing, and gateway configuration validation for Kong, Envoy, and AWS API Gateway.

PramodDutta/qaskills · 43 tokens