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 New1Direction/korgex --skill designing-a-job-queuegit clone --depth 1 https://github.com/New1Direction/korgexWrote 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/new1direction/korgex/designing-a-job-queue)<a href="https://agentmods.dev/skills/new1direction/korgex/designing-a-job-queue"><img src="https://agentmods.dev/badge/skills/new1direction/korgex/designing-a-job-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.00021 | $0.00361 |
| Opus 5 | $0.00010 | $0.00180 |
| Sonnet 5 | $0.00004 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
designing-a-job-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 8d 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.
What it actually says
When work is slow, scheduled, or should survive a restart, push it to a queue and process it with workers. The hard part isn't enqueuing — it's reliability.
- Make jobs idempotent. A job WILL run more than once (retries, redelivery, crashes). Design so running it twice is safe — key on a stable id, check "already done" before acting.
- At-least-once, not exactly-once. Assume duplicates and out-of-order delivery; exactly-once is largely a myth. Idempotency (point 1) is how you cope.
- Acknowledge after success. Mark a job done only once the work committed. If a worker dies mid-job, the un-acked job should redeliver, not vanish.
- Bound retries + dead-letter. Retry with backoff up to a limit; send permanent failures to a dead-letter queue for inspection — never retry forever.
- Visibility/lease timeouts. A claimed job must reappear if the worker stalls; tune the lease so it doesn't double-run a still-healthy job.
- Backpressure + concurrency limits. Cap workers so the queue can't overwhelm downstream (the DB, an API). Monitor depth and age — a growing backlog is a signal.
- Observe it (see observability-and-logging): job counts, failures, latency, queue depth. A silent queue is a queue you'll discover broken too late.
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.
- 8d ago First seen · 26 lines · 21 tokens per session scan A d2e38a47abc6
designing-a-job-queue is a skill published in the GitHub repository New1Direction/korgex (5 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 361 once invoked, about $0.0001 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.
Other skills, from other repositories
telegram
Owner-only Telegram text bridge and Mini App gateway for the existing Ouroboros interface.
provide
Turn the owner's API, model, or dataset into a paid service on the platform's services catalog: build the wrapper endpoint, self-test it against the admission probe, and hand the owner the values the listing form needs. Use when the owner wants to sell or list something they already run as a metered service.
api-verification
An API verification workflow that creates both an .http request file and a .cjs JavaScript file, then runs an automation script to test them. An API is an interface through which software exchanges requests and responses.
api-contract-architecture
An architecture guide for public APIs, including HTTP services, software-development kits, command-line tools, schemas, types, errors, pagination, filtering, and compatibility.
backend-domain-architecture
A review guide for backend and business-domain design. It examines business rules, workflows, permissions, APIs, transactions, consistency, repeated requests, compatibility, data boundaries, and service responsibilities.
distributed-systems-architecture
An architecture guide for distributed systems—software split across services that communicate over networks.