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 agent-sh/glidemq --skill glide-mqgit clone --depth 1 https://github.com/agent-sh/glidemqWrote 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/agent-sh/glidemq/glide-mq)<a href="https://agentmods.dev/skills/agent-sh/glidemq/glide-mq"><img src="https://agentmods.dev/badge/skills/agent-sh/glidemq/glide-mq/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/agent-sh/glidemq/glide-mq"><img src="https://agentmods.dev/badge/skills/agent-sh/glidemq/glide-mq.svg" alt="Reviewed on agentmods" width="80" 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.00070 | $0.01578 |
| Opus 5.5 | $0.00028 | $0.00631 |
| Sonnet 5.5 | $0.00014 | $0.00316 |
| Haiku 4.5 | $0.00007 | $0.00158 |
Grade A, and why
glide-mq 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 14d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
glide-mq
Job queue for Node.js on Valkey/Redis Streams, with a Rust NAPI client and all queue logic in Valkey Server Functions (one FCALL per job operation). The API is close to BullMQ; the differences that bite are in connection config and a few method signatures.
Quick Start
import { Queue, Worker } from 'glide-mq';
const connection = { addresses: [{ host: 'localhost', port: 6379 }] };
const queue = new Queue('tasks', { connection });
await queue.add('send-email', { to: '[email protected]', subject: 'Hello' });
const worker = new Worker(
'tasks',
async (job) => {
console.log(`Processing ${job.name}:`, job.data);
return { sent: true };
},
{ connection, concurrency: 10 },
);
worker.on('completed', (job) => console.log(`Done: ${job.id}`));
worker.on('failed', (job, err) => console.error(`Failed: ${job.id}`, err.message));
References
Read the file that matches the task; each holds the options, defaults and edge cases for its area.
| Area | File |
|---|---|
| Queues, adding jobs, retries, dedup, rate limits, job lookup | references/queue.md |
| Workers, concurrency, batch mode, stalled jobs, sandboxing | references/worker.md |
| Connection options, TLS, IAM, cluster, AZ affinity | references/connection.md |
Parent-child flows, DAGs, chain / group / chord |
references/workflows.md |
Fan-out with Broadcast / BroadcastWorker |
references/broadcast.md |
| Cron and interval schedulers | references/schedulers.md |
QueueEvents, metrics, OpenTelemetry |
references/observability.md |
| LLM usage, token streaming, suspend/resume, budgets, fallbacks, token rate limits | references/ai-native.md |
| Vector search over jobs | references/search.md |
| Serverless producers, HTTP proxy and SSE, in-memory testing | references/serverless.md |
What ships with it
10 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.
- references/ai-native.md 13 KB
- references/broadcast.md 5.3 KB
- references/connection.md 5.3 KB
- references/observability.md 6.4 KB
- references/queue.md 8.0 KB
- references/schedulers.md 3.5 KB
- references/search.md 6.3 KB
- references/serverless.md 8.8 KB
- references/worker.md 8.6 KB
- references/workflows.md 7.3 KB
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.
- 14d ago Changed 70d32c20b690
- 27d ago Changed · -40 lines · -128 tokens per session 6196b2617ee8
- 1mo ago First seen · 221 lines · 198 tokens per session scan A 5c5ac4df11e8
glide-mq is a skill published in the GitHub repository agent-sh/glidemq (3 stars, last pushed 15d ago), licensed Apache-2.0. It adds 70 tokens to every session and 1,578 once invoked, about $0.0003 per session on Opus 5.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
using-redis-token-buckets
Use when adding a bucket-like rate limit backed by Redis: a per-caller budget with burst capacity and continuous refill, a refund path for requests that did no work, or a limit whose Retry-After must be a real wait rather than a window edge. posthog/tokenbucket.py provides an atomic Lua token bucket (consume, refund…
spring-data-redis
Use when implementing caching, session storage, rate limiting, or any Redis integration. Covers cache-aside pattern, key naming, TTL strategy, and serialization config.
using-redis-token-buckets
Use when adding a bucket-like rate limit backed by Redis: a per-caller budget with burst capacity and continuous refill, a refund path for requests that did no work, or a limit whose Retry-After must be a real wait rather than a window edge. posthog/tokenbucket.py provides an atomic Lua token bucket (consume, refund…
bull-mq
Runs background jobs in Node.js with BullMQ, a job queue library backed by Redis (or PostgreSQL since v6): delayed and prioritized jobs, retries with backoff, rate limiting, cron-style job schedulers, parent-child flows and concurrency control. Use when a user asks to add a background worker, queue emails or webhooks…
cache-strategy
Design and implement caching layers for APIs and web applications using Redis or Memcached. Use when you need to reduce database load, improve response times, or handle traffic spikes. Covers cache-aside, write-through, and write-behind patterns, TTL strategies, cache invalidation, and stampede prevention. Trigger…
python-redis-module-skill
A Python integration guide for adding Redis to an existing FastAPI project. Redis is a fast shared data store commonly used for temporary data, sessions, locks, counters, and messages.