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 instructions/agent-sh/glidemq/agents-mdgit clone --depth 1 https://github.com/agent-sh/glidemqWhat 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.00414 | $0.00414 |
| Opus 5 | $0.00207 | $0.00207 |
| Sonnet 5 | $0.00083 | $0.00083 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
glidemq AGENTS.md 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 yesterday.
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.
This is a copy
86% identical to agentsys CLAUDE.md — 13 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
glidemq
glide-mq message queue skills - greenfield development and migration from BullMQ/Bee-Queue
Skills
- glide-mq
- glide-mq-migrate-bullmq
- glide-mq-migrate-bee
Critical Rules
- Plain text output - No emojis, no ASCII art. Use
[OK],[ERROR],[WARN],[CRITICAL]for status markers. - No unnecessary files - Don't create summary files, plan files, audit files, or temp docs.
- Task is not done until tests pass - Every feature/fix must have quality tests.
- Create PRs for non-trivial changes - No direct pushes to main.
- Always run git hooks - Never bypass pre-commit or pre-push hooks.
- Use single dash for em-dashes - In prose, use
-(single dash with spaces), never--. - Report script failures before manual fallback - Never silently bypass broken tooling.
- Token efficiency - Save tokens over decorations.
Model Selection
| Model | When to Use |
|---|---|
| Opus | Complex reasoning, analysis, planning |
| Sonnet | Validation, pattern matching, most agents |
| Haiku | Mechanical execution, no judgment needed |
Core Priorities
- User DX (plugin users first)
- Worry-free automation
- Token efficiency
- Quality output
- Simplicity
Dev Commands
npm test # Run tests
References
- Part of the agentsys ecosystem
- https://agentskills.io
- glide-mq docs: https://avifenesh.github.io/glide-mq.dev/
- glide-mq repo: https://github.com/avifenesh/glide-mq
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.
- yesterday First seen · 50 lines · 414 tokens per session scan A 1d646414dae2
glidemq AGENTS.md is an instructions file published in the GitHub repository agent-sh/glidemq (5 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 414 tokens to every session, about $0.0021 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to agentsys CLAUDE.md, differing in 13 lines, and is treated as a copy.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
buildNext
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.