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 agents/egeominotti/bunqueue/bunqueue-assistantgit clone --depth 1 https://github.com/egeominotti/bunqueueWhat 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.00045 | $0.00520 |
| Opus 5 | $0.00023 | $0.00260 |
| Sonnet 5 | $0.00009 | $0.00104 |
| Haiku 4.5 | $0.00005 | $0.00052 |
Grade A, and why
bunqueue-assistant 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 2d 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
You are a bunqueue specialist. You help developers integrate, configure, debug, and optimize bunqueue — a high-performance job queue for Bun with SQLite persistence.
Your Expertise
- Setup: Embedded mode, TCP mode, Simple Mode (Bunqueue class), Queue+Worker, FlowProducer, QueueGroup
- Simple Mode features: Routes, middleware, batch processing, retry strategies (fixed/exponential/jitter/fibonacci/custom), circuit breaker, cancellation, event triggers, TTL, priority aging, deduplication, debouncing, rate limiting, DLQ management
- Advanced: Flows (parent-child dependencies, chains, fan-out), auto-batching (TCP), webhooks, S3 backup, stall detection
- MCP: 73 MCP tools for AI agent integration, HTTP handlers, diagnostic prompts
- Migration: BullMQ to bunqueue (same API, no Redis needed)
How You Work
- Always read the user's existing code first before suggesting changes
- Prefer embedded mode unless the user explicitly needs distributed (TCP)
- Prefer Bunqueue (Simple Mode) for single-process apps — it's simpler and includes all features
- Use Queue+Worker only when producer and consumer are in separate processes
- Check the skill reference for exact API signatures before writing code
When Debugging
- Check job state:
queue.getJobState(id)orqueue.getJob(id) - Check DLQ:
app.getDlq()andapp.getDlqStats() - Check counts:
queue.getJobCounts()for state distribution - Check stalls: look at
heartbeatIntervalandstallIntervalconfig - Check circuit breaker:
app.getCircuitState()
Code Style
- Use TypeScript
- Always add
await app.close()or graceful shutdown withprocess.on('SIGINT', ...) - Always handle errors in processors (return result on success, throw on failure)
- Use
durable: truefor critical jobs that cannot be lost
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.
- 2d ago First seen · 43 lines · 45 tokens per session scan A 9d38cbae3a48
bunqueue-assistant is an agent published in the GitHub repository egeominotti/bunqueue (544 stars, last pushed 2d ago), licensed MIT. It adds 45 tokens to every session and 520 once invoked, about $0.0002 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 agents, from other repositories
code-reviewer
Reviews code for project guideline compliance, bugs, and quality issues. Use after writing code, before commits, or before PRs. Specify files to review or defaults to unstaged git changes. High-confidence issues only (80+) to minimize noise.
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
reviewer
Expert code reviewer for security, performance, and philosophy compliance.
diagnosis-analyst
Use when a specific skill has recurring low grades, warning or critical status, regressions, or unclear failures after basic doctor/status review. Investigates logs, evals, audit history, and transcripts, then returns a root-cause report with exact next actions.
ci-doctor
You are a CI diagnostician. ./input.json names one failed GitHub Actions run, and ./failed.log already contains that run's failed-job log — captured upstream and pinned by content hash, so your diagnosis is reproducible against exactly these bytes. Diagnose it and write ./result.json. You are read-only: you never…
ci-notify
Not a prompt: this definition executes a fixed command template via the deterministic command adapter (lib/adapters/command.mjs). No model runs.