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/mergifyio/mergify-cli/mergify-eventsnpx skills add Mergifyio/mergify-cli --skill mergify-eventsgit clone --depth 1 https://github.com/Mergifyio/mergify-cliWrote 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/mergifyio/mergify-cli/mergify-events)<a href="https://agentmods.dev/skills/mergifyio/mergify-cli/mergify-events"><img src="https://agentmods.dev/badge/skills/mergifyio/mergify-cli/mergify-events.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.00131 | $0.01116 |
| Opus 5 | $0.00066 | $0.00558 |
| Sonnet 5 | $0.00026 | $0.00223 |
| Haiku 4.5 | $0.00013 | $0.00112 |
Grade A, and why
mergify-events 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mergify Events
Overview
mergify events lists the repository's Mergify activity log as a timeline — the ~45 event types the engine records: the action.queue.* lifecycle, workflow actions (action.merge, action.rebase, action.label, …), user commands (command.queue, command.dequeue), ci_insights.*, queue pauses, and scheduled freezes. One command over filters; there is deliberately no command per event type.
mergify events # whole repo, last 24h
mergify events --pr 1740 # one PR's events, last 24h
mergify events --pr 1740 --since 7d # wider window (s/m/h/d/w, max 90d)
mergify events --type action.queue.leave --type command.queue # filter, repeatable
mergify events --pr 1740 --json # raw events, newest first
mergify events --limit 20 # newest 20 only (the header says so)
The window rule (the one thing to get right)
Every result covers an explicit time window, stated in the header and in the empty-case message:
PR #1740 · 6 events · 2026-07-29 21:00 → 2026-07-30 21:00 UTC
- Default window: the last 24 hours. A PR dequeued last week shows nothing in the default window — that is "nothing in the last 24h", never "no history".
- Retention is 90 days;
--since 90dis the widest useful window. Anything wider is rejected up front with the fix in the message. - An empty result names the window:
No events for PR #1740 between <from> and <to> UTC.If you did not search the full retention yet, widen with--since 90dbefore concluding anything.
Reading the timeline
Oldest first (it reads down the page), with a summary per event where the metadata carries one:
2026-07-30
14:02 action.queue.enter default
14:31 action.queue.checks_start default · draft PR #1801
15:04 action.queue.checks_end CHECKS_RETRIED
15:04 action.queue.leave CHECKS_FAILED
15:12 command.queue @jd
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 · 69 lines · 131 tokens per session scan A 234b5305b737
mergify-events is a skill published in the GitHub repository Mergifyio/mergify-cli (30 stars, last pushed today), licensed Apache-2.0. It adds 131 tokens to every session and 1,116 once invoked, about $0.0007 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…