thufir vs incident-response
thufir is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑22.
thufir is a plugin bundle for AI coding tools published by Evangelos Meklis. No marketplace we read lists it any more. incident-response is a plugin bundle for AI coding tools published by Grey Haven Studio. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-28. 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 | ||
|---|---|---|
| Community marketplace evangelosmeklis/thufir | Removed on 2026-10-22 Version: 1.0.0 Forks (GitHub): 1 Stars (GitHub): 7 Not marked · First seen |
Not listed |
| Community marketplace greyhaven-ai/claude-code-config | Not listed | Listed Version: 2.1.0 Forks (GitHub): 5 Stars (GitHub): 31 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 | thufirno longer listed · | incident-response |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 7 | 31 |
| Forks (GitHub) (differs) | 1 | 5 |
| Last release | Not published | Not published |
| Where it runs | Installs as a plugin bundle | Installs as a plugin bundle |
| Transport | Not stated | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 6, secrets among them: 3 | Not published |
| Parts of the bundle (differs) | 11 | 5 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/evangelosmeklis/thufir | github.com/greyhaven-ai/claude-code-config |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-18 | 2026-10-20 |
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 thufir
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Handle production incidents end to end: cloud log and metric investigation, outage triage, Kubernetes platform SRE work, blameless postmortems, auditable bug receipts…
-
Enhance code quality and security through PagerDuty risk scoring and incident correlation. Score pre-commit diffs against historical incident data and surface deployment risk…
-
Alex — CodeMinder AI solutions engineer. Connects user pain, system signals, and business impact into Ground Truth for your engineering roadmap. Book demos, explore the design…
-
Site reliability engineering and incident response expert
-
Error tracing, root cause analysis, and smart debugging for production systems
-
Error tracing, root cause analysis, and smart debugging for production systems
What each says it does
thufir
Root cause analysis plugin integrating Prometheus, GitHub, and GitLab for production incident investigation
incident-response
Production incident response system with incident management workflows, intelligent debugging, runbook automation, and postmortem generation. Handles incident detection, triage, mitigation, and learning.
How to run each
thufir
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
incident-response As a Claude Code plugin
/plugin marketplace add greyhaven-ai/claude-code-config
/plugin install incident-response@grey-haven-plugins
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 incident-response publish no settings it asks for, so we do not compare settings.
What it can do: thufir · What it can do: incident-response · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.