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 skills add JansenAnalytics/claudex --skill task-queuegit clone --depth 1 https://github.com/JansenAnalytics/claudexWrote 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/skills/jansenanalytics/claudex/task-queue)<a href="https://agentmods.dev/skills/jansenanalytics/claudex/task-queue"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/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.00060 | $0.01632 |
| Opus 5 | $0.00030 | $0.00816 |
| Sonnet 5 | $0.00012 | $0.00326 |
| Haiku 4.5 | $0.00006 | $0.00163 |
Grade A, and why
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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: task-queue
A persistent, JSON-backed job queue. Lets Kite schedule and manage shell commands without raw cron. One-shot tasks (run at a specific time) and recurring tasks (cron schedule) are both supported.
Trigger phrases
- "schedule a task / job"
- "run [command] at [time]"
- "run [command] every [N] minutes/hours"
- "add to the task queue"
- "what tasks are scheduled / queued"
- "list my tasks"
- "cancel task [id]"
- "clear done tasks"
- "task status [id]"
Files
| File | Purpose |
|---|---|
${TASK_QUEUE_HOME:-$HOME/projects/task-queue}/queue.json |
Task store (source of truth) |
${TASK_QUEUE_HOME:-$HOME/projects/task-queue}/cli.cjs |
CLI tool for managing tasks |
${TASK_QUEUE_HOME:-$HOME/projects/task-queue}/runner.cjs |
Runner — executes due tasks |
${TASK_QUEUE_HOME:-$HOME/projects/task-queue}/runner.log |
Runner output log |
Skill copies live in ${CLAUDE_SKILLS_DIR:-$HOME/.claude-agent/.claude/skills}/task-queue/scripts/.
Quick reference
# Add one-shot task
node ${TASK_QUEUE_HOME:-$HOME/projects/task-queue}/cli.cjs add "name" "command" --at "2026-02-21T18:00:00"
# Add recurring task (every 15 min)
node ${TASK_QUEUE_HOME:-$HOME/projects/task-queue}/cli.cjs add "name" "command" --every "*/15 * * * *"
# Add immediate task (runs next runner tick)
node ${TASK_QUEUE_HOME:-$HOME/projects/task-queue}/cli.cjs add "name" "command"
# List all / filter
node ${TASK_QUEUE_HOME:-$HOME/projects/task-queue}/cli.cjs list
node ${TASK_QUEUE_HOME:-$HOME/projects/task-queue}/cli.cjs list --status pending
# Details for one task
node ${TASK_QUEUE_HOME:-$HOME/projects/task-queue}/cli.cjs status <id>
# Cancel / mark done
node ${TASK_QUEUE_HOME:-$HOME/projects/task-queue}/cli.cjs cancel <id>
node ${TASK_QUEUE_HOME:-$HOME/projects/task-queue}/cli.cjs done <id>
# Housekeeping
node ${TASK_QUEUE_HOME:-$HOME/projects/task-queue}/cli.cjs clear --done
node ${TASK_QUEUE_HOME:-$HOME/projects/task-queue}/cli.cjs clear --failed
node ${TASK_QUEUE_HOME:-$HOME/projects/task-queue}/cli.cjs clear --all
# Run runner manually (normally cron does this)
node ${TASK_QUEUE_HOME:-$HOME/projects/task-queue}/runner.cjs
# Tail log
tail -f ${TASK_QUEUE_HOME:-$HOME/projects/task-queue}/runner.log
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 182 lines · 60 tokens per session scan A fd806b0ca5ec
task-queue is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 1,632 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-09-03.
Other skills, from other repositories
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
wp-content-workflows
This skill should be used when the user asks about "workflow automation", "triggers", "scheduled tasks", "WP-Cron", "content publishing triggers", "hook-based actions", "post status transitions", "automated notifications", "workflow triggers", "event-driven actions", "content lifecycle hooks", "multi-channel actions"…
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
subscription-manager
Create and manage scheduled subscription tasks. Use when the user wants to set up recurring reminders, periodic reports, scheduled checks, or any automated tasks that run on a schedule. Supports cron expressions, fixed intervals, and one-time executions.