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 skills/longbkit/clisbot/queue-workflownpx skills add longbkit/clisbot --skill queue-workflowgit clone --depth 1 https://github.com/longbkit/clisbotWhat 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.00062 | $0.01608 |
| Opus 5 | $0.00031 | $0.00804 |
| Sonnet 5 | $0.00012 | $0.00322 |
| Haiku 4.5 | $0.00006 | $0.00161 |
Grade A, and why
queue-workflow 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Queue Workflow
Use this skill when a task needs more than one serious pass, or when the user explicitly asks for queue workflow.
Problem
AI can fail in two opposite ways:
- stop early, act lazy, or treat a green first pass as done
- keep "improving" by adding duplicate sections, files, functions, fallbacks, names, or explanations
Queue workflow protects against both. It also catches prompt echoing, history leaking, topic drift away from exact continue, shallow queued micro-tasks, and review overload for the human.
The goal is not to split work into tiny tasks. Each pass, including the current pass and every later queue-runner invocation, must inspect context, do the work, validate, simplify, and report clearly.
When To Use
Use queue-first when:
- the user explicitly asks for queue workflow, even for small work
- the task is medium or large
- code, docs, skill, runbook, or architecture changes may sprawl
- regressions, missing tests/docs, naming drift, or duplicate structure are plausible
- the user needs a final version, not draft-history explanation inside the artifact
Skip it only when the user did not ask for queue workflow and the task is clearly tiny, low-risk, and fully verifiable in one short pass.
Read references/content-architecture.md as the structural foundation for both the current pass and queued passes.
Core Workflow
Principles:
- Durable queues are an external clisbot queue-runner flow; the current agent must not drain pending queue items locally.
- Queuing follow-up work never lowers the quality bar for the current pass.
- Run the current pass deeply and thoroughly before reporting: inspect state, edit, validate, simplify, and name what is done now.
- When the queue runner invokes a queued prompt later, that invocation must also run as a full-quality session, not a small visible micro-task.
- Preserve the current thread with exact
continuebefore switching to a new lens. - At queue creation time, do not depend on knowing whether a future pass will finish cleanly; add the control prompts up front after important milestones.
- Keep final artifacts clean: do not echo user wording or leak draft-history notes unless the user needs a changelog.
What ships with it
2 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 · 134 lines · 62 tokens per session scan A 535d96386d8e
queue-workflow is a skill published in the GitHub repository longbkit/clisbot (114 stars, last pushed 3d ago), licensed MIT. It adds 62 tokens to every session and 1,608 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.
Other skills, from other repositories
chatbot
Use when a support or sales bot on a live website must behave: persona/system prompt, grounding so it cannot invent prices or policy, jailbreak and injection defense, the human handoff, launch metrics and kill switch. NOT the agent loop or RAG index under it (that is building-agents), NOT a human answering one ticket…
create-ppt
Creates polished PowerPoint presentations with dark-first design, custom palettes, charts, and tables. Use when creating, designing, or generating PPTX slide decks or presentations.
create-pdf
Guidelines for creating polished, themed PDF reports with the code execution tool.
skill-authoring-best-practices
Best practices for writing effective Skills that are discoverable, concise, and reliable. Use when creating, reviewing, or improving Skills.
cloud_storage
Skill for uploading and downloading files from cloud storage (AWS S3 or Azure Blob Storage).
sandbox_file_manager
Use this skill when you need to manage files inside the active remote or local sandbox, including listing sandbox files, downloading files from the sandbox to the local backend, or uploading local backend files to the sandbox.