debian-packaging vs ExecBro
debian-packaging is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑20.
debian-packaging is a plugin bundle for AI coding tools published by Brian Cosgrove. No marketplace we read lists it any more. ExecBro is an MCP server published by execbro.com. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-20. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  ExecBro | |
|---|---|---|
| Community marketplace cosgroveb/debian-packaging-agent-skill | Removed on 2026-10-20 Version: 0.1.0 Forks (GitHub): 2 Stars (GitHub): 5 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.18.0 Downloads/month (npm): 4 348 Downloads/week (npm): 651 Forks (GitHub): 9 Stars (GitHub): 79 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 2.18.0 Downloads/month (npm): 4 348 Downloads/week (npm): 651 Forks (GitHub): 9 Stars (GitHub): 79 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 | debian-packagingno longer listed · | ExecBro |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 5 | 79 |
| Forks (GitHub) (differs) | 2 | 9 |
| Last release (differs) | Not published | 2026-10-20 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (execbro) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/cosgroveb/debian-packaging-agent-skill | github.com/igorzheludkov/execbro |
| Changes in the last 7 days (differs) | 4 | 6 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of debian-packaging
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Linux packaging and release workflows — Debian/.deb builds, npm publishing, GitHub release creation, agent deploy scripts, and local debugging
-
Rust, Cargo, crate, test, CI, and package workflows.
-
Go-specific development tools with best practices
-
Expert agents for specific programming languages (Python, Go, Rust, etc.)
-
rust-skills
Rust development best practices and coding standards
-
DevOps automation skills for full software development lifecycle. 20 skills covering code analysis, design, implementation, testing, code review, refactoring, documentation…
What each says it does
debian-packaging
Debian packaging skill covering policy, debhelper, and language-specific packaging for Ruby, Python, Rust, and Go.
ExecBro
Gives AI agents eyes and hands into running React Native apps: logs, REPL, tap, screenshots
How to run each
debian-packaging
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
ExecBro As a local MCP server: npm package
claude mcp add --transport stdio execbro -- npx -y execbroCommands 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 debian-packaging publish no settings it asks for, so we do not compare settings.
What it can do: debian-packaging · What it can do: ExecBro · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.