gimme-the-lint vs io.github.invigil/invigil
gimme-the-lint is a plugin bundle for AI coding tools published by TheGlitchKing. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.invigil/invigil is an MCP server published by invigil. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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
| Marketplace |  gimme-the-lint |  io.github.invigil/invigil |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 2.8.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.7.1 Downloads/month (PyPI): 191 Downloads/week (PyPI): 33 Forks (GitHub): 4 Stars (GitHub): 1 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
| Fact | gimme-the-lint | io.github.invigil/invigil |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 4 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (invigil) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 10 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/theglitchking/gimme-the-lint | github.com/invigil/invigil |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
gimme-the-lint
Progressive linting system that only blocks on new violations, never on legacy code. Baselines existing lint issues by directory, then enforces clean code going forward. Supports Python (Ruff) and JavaScript/TypeScript (ESLint) in monorepo configurations. Includes drift detection, auto-healing, git hooks, and a GitHub Action for CI enforcement. Directory-chunked baselines allow gradual adoption without a big-bang cleanup.
io.github.invigil/invigil
Linters check your code. Invigil checks whether your repo is legible — to newcomers and AI agents.
How to run each
gimme-the-lint As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install gimme-the-lint@claude-communityio.github.invigil/invigil As a local MCP server: PyPI package
claude mcp add --transport stdio invigil -- uvx --from "invigil[mcp]" invigil mcpCommands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: gimme-the-lint · What it can do: io.github.invigil/invigil · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.