Ext Ops Panel
Open dashboard
Comparison

prompt-engineering vs Promptheus

prompt-engineering is a plugin bundle for AI coding tools published by duyet. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Promptheus is an MCP server published by abhichandra21. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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
Marketplaceprompt-engineeringPromptheus
Community marketplace duyet/codex-claude-plugins Listed
Version: 1.2.0
Forks (GitHub): 1
Stars (GitHub): 15
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.1
Downloads/month (PyPI): 98
Downloads/week (PyPI): 36
Forks (GitHub): 0
Stars (GitHub): 17
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

prompt-engineering vs Promptheus
Factprompt-engineeringPromptheus
Marketplaces that list it11
Stars (GitHub) (differs)15 (worse)17 (better)
Forks (GitHub) (differs)1 (better)0 (worse)
Last release (differs)2026-10-19Not published
Where it runs (differs)Installs as a plugin bundleOn your machine (promptheus)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published8, secrets among them: 6
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/duyet/codex-claude-pluginsgithub.com/abhichandra21/promptheus
Changes in the last 7 days (differs)70
First seen (differs)2026-10-162026-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

prompt-engineering

In its own words, on Community GitHub marketplaces:

Prompting guidance and per-model deltas for Claude, Gemini, and Grok.

Promptheus

In its own words, on Official MCP Registry:

AI-powered prompt refinement with adaptive questioning and multi-provider support (6+ LLM backends)

How to run each

prompt-engineering As a Claude Code plugin

Claude Code
/plugin marketplace add duyet/codex-claude-plugins
/plugin install prompt-engineering@duyet-claude-plugins

Promptheus As a local MCP server: PyPI package

Claude Code
claude mcp add --env "ANTHROPIC_API_KEY=<YOUR_ANTHROPIC_API_KEY>" --env "GLM_API_KEY=<YOUR_GLM_API_KEY>" --env "GOOGLE_API_KEY=<YOUR_GOOGLE_API_KEY>" --env "GROQ_API_KEY=<YOUR_GROQ_API_KEY>" --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --env "QWEN_API_KEY=<YOUR_QWEN_API_KEY>" --transport stdio promptheus -- uvx promptheus

Requires: ANTHROPIC_API_KEY (secret), GLM_API_KEY (secret), GOOGLE_API_KEY (secret), GROQ_API_KEY (secret), OPENAI_API_KEY (secret), QWEN_API_KEY (secret)

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 prompt-engineering publish no settings it asks for, so we do not compare settings.

What it can do: prompt-engineering · What it can do: Promptheus · 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. 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