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/agent-sh/glidemq/glide-mqnpx 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.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 | $0.00198 | $0.02408 |
| Opus 5 | $0.00099 | $0.01204 |
| Sonnet 5 | $0.00040 | $0.00482 |
| Haiku 4.5 | $0.00020 | $0.00241 |
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 4d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
glide-mq
High-performance AI-native message queue for Node.js on Valkey/Redis Streams with a Rust NAPI core.
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));
When to Apply
Use this skill when:
- Creating or configuring queues, workers, or producers
- Adding jobs (single, bulk, delayed, priority)
- Setting up retries, backoff, or dead-letter queues
- Building job workflows (parent-child, DAGs, chains)
- Implementing fan-out broadcast patterns
- Configuring cron/interval schedulers
- Setting up connection options (TLS, IAM, AZ-affinity)
- Working with batch processing or rate limiting
- Tracking AI/LLM usage (tokens, cost, model) per job or flow
- Streaming LLM output tokens in real-time
- Implementing human-in-the-loop approval with suspend/resume
- Setting budget caps (tokens, cost) on workflow flows
- Configuring fallback chains for model/provider failover
- Dual-axis rate limiting (RPM + TPM) for LLM API compliance
- Aggregating rolling usage/cost summaries across queues
- Searching jobs by vector similarity (KNN) with Valkey Search
- Exposing queues or broadcasts over the HTTP proxy, including SSE endpoints
- Integrating with frameworks (Hono, Fastify, NestJS, Hapi)
- Deploying in serverless environments (Lambda, Vercel Edge)
Core API by Priority
| Priority | Category | Impact | Reference |
|---|---|---|---|
| 1 | Queue & Job Operations | CRITICAL | references/queue.md |
| 2 | Worker & Processing | CRITICAL | references/worker.md |
| 3 | Connection & Config | HIGH | references/connection.md |
| 4 | Workflows & FlowProducer | HIGH | references/workflows.md |
| 5 | Broadcast (Fan-Out) | MEDIUM | references/broadcast.md |
| 6 | Schedulers (Cron/Interval) | MEDIUM | references/schedulers.md |
| 7 | Observability & Events | MEDIUM | references/observability.md |
| 8 | AI-Native Primitives | HIGH | references/ai-native.md |
| 9 | Vector Search | MEDIUM | references/search.md |
| 10 | Serverless & Testing | LOW | 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 4.4 KB
- references/connection.md 5.3 KB
- references/observability.md 6.4 KB
- references/queue.md 8.0 KB
- references/schedulers.md 3.3 KB
- references/search.md 6.3 KB
- references/serverless.md 8.7 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.
- 4d 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 (5 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 198 tokens to every session and 2,408 once invoked, about $0.0010 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
redis-inspect
Inspect Redis cache keys, values, and TTLs for debugging. Supports both main cache and system cache. Use for debugging cache issues, checking cached values, and monitoring cache state. Read-only by default.
redis-js
Work with the Upstash Redis JavaScript/TypeScript SDK for serverless Redis operations. Use for caching, session storage, rate limiting, leaderboards, full-text search (querying, filtering, aggregating with @upstash/redis search extension), and all Redis data structures. Supports automatic serialization/deserialization…
caching-strategies
CDN, Redis, in-memory cache, cache invalidation, and distributed caching patterns.
background-job-orchestrator
Expert in background job processing with Bull/BullMQ (Redis), Celery, and cloud queues. Implements retries, scheduling, priority queues, and worker management. Use for async task processing, email campaigns, report generation, batch operations. Activate on "background job", "async task", "queue", "worker", "BullMQ"…
bun-redis
Use when working with Redis in Bun (ioredis, Upstash), caching, pub/sub, session storage, or key-value operations.
nw-database-technology-selection
Database comparison catalogs, RDBMS vs NoSQL selection criteria, CAP/ACID/BASE theory, OLTP vs OLAP, and technology-specific characteristics.