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/standardbeagle/agnt/messaging-queuenpx skills add standardbeagle/agnt --skill messaging-queuegit clone --depth 1 https://github.com/standardbeagle/agntWhat 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.00043 | $0.02931 |
| Opus 5 | $0.00022 | $0.01465 |
| Sonnet 5 | $0.00009 | $0.00586 |
| Haiku 4.5 | $0.00004 | $0.00293 |
Grade A, and why
messaging-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 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.
How it starts
The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Messaging Queue Coordination
Use this skill when touching any code that delivers events to an AI agent — PTY stdin injection, MCP Log() notifications, channel pings, overlay toasts, hold buffers, alert hubs, or auto-forward paths. Every "spamming the agent" bug we have shipped traces back to violating one of the rules below.
The Single-Queue Rule
There is exactly one ordered pipeline from "raw event" to "agent's input". Anything that writes to the agent surface MUST flow through it. Parallel writes are bugs, even when they "work" most of the time — they bypass dedup, activity-deferral, outage-holds, and ordering, and they are the canonical cause of repeated-message spam.
Currently in this project the canonical queue is internal/overlay/alerts.go::AlertScanner (process-output side) plus the daemon-side gate chain in internal/daemon/hub_helpers.go::wireProxyLogger (proxy-side).
Resolved (PTY side): the browser-error / auto-forward path
cmd/agnt/overlay.go::processAutoForwardEvent no longer writes the PTY
directly. It cascade-filters then calls AlertScanner.Inject, so browser-JS
and HTTP errors now share the same dedup / batch / overload-throttle /
activity-defer queue as process-output alerts. The old lastForwardNs global
single-timestamp debounce has been removed. The remaining direct typeText
in processProxyEvent is for non-error UI/automation events (panel messages,
sketch, design) only — error sources all flow through the queue.
Still parallel (cross-process, low incidence): the daemon incident
pipeline delivers to MCP-native agents via incident_digest → session.Log()
(consumed only by agnt mcp, serve.go), while PTY-wrapped agents get stdin
injection via the overlay socket (consumed by agnt run). These serve
different consumer processes / different agents (MCP-native vs PTY-only), so
the same agent does not normally get both. A single agent that is both
MCP-connected and under agnt run could double-receive; per-session
delivery-mode routing (adapter identity → mcp|stdin) is the intended fix and
is not yet wired.
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 · 154 lines · 43 tokens per session scan A e307ef6ab959
messaging-queue is a skill published in the GitHub repository standardbeagle/agnt (19 stars, last pushed 3d ago), licensed Apache-2.0. It adds 43 tokens to every session and 2,931 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 skills, from other repositories
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
browser_cdp
通过 Chrome DevTools Protocol (CDP) 连接已运行的浏览器，或扫描本机 CDP 端口，用于远程调试与多工具共享浏览器实例。.