Ext Ops Panel
Open dashboard
Comparison

Waggle vs idle-timing

Waggle is a plugin bundle for AI coding tools published by Abhigyan Shekhar. Marketplaces we read that list it: 1 (Community GitHub marketplaces). idle-timing is a plugin bundle for AI coding tools published by clankercode. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-11-07. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceWaggleidle-timing
Community marketplace abhigyan-shekhar/waggle-mcp Listed
Version: 0.1.3
Forks (GitHub): 137
Stars (GitHub): 44
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 0.4.0
Forks (GitHub): 1
Stars (GitHub): 5
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Waggle vs idle-timing
FactWaggleidle-timing
Marketplaces that list it11
Stars (GitHub) (differs)44 (better)5 (worse)
Forks (GitHub) (differs)137 (better)1 (worse)
Last releaseNot publishedNot published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)6, secrets among them: 0Not published
Hooks it runs (differs)Not published3
Parts of the bundle (differs)56
Licence (differs)Apache-2.0Unlicense OR CC0-1.0
Repository (differs)github.com/abhigyan-shekhar/waggle-mcpgithub.com/clankercode/claude-inject-idle-time
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Waggle

In its own words, on Community GitHub marketplaces:

Local graph memory that lets Codex recall project context across sessions.

idle-timing

In its own words, on Claude Code: claude-plugins-community:

- Injects timing block to prompts (not user-visible) covering local date-time, idle time (since agent turn ended), and prior turn execution time. - Shows `[after Xm Ys]` to user via post submit hook to indicate how long it was between that prompt and agent finishing prior turn. - Provides statusline integration for idle time.

How to run each

Waggle As a Codex plugin

Codex
codex plugin marketplace add abhigyan-shekhar/waggle-mcp

idle-timing As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install idle-timing@claude-community

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of idle-timing publish no settings it asks for, so we do not compare settings.

What it can do: Waggle · What it can do: idle-timing · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built