Model or dataset
NeoVertex1/SuperPrompt avatar
NeoVertex1/SuperPrompt

SuperPrompt: A Prompt File That Rewrites Its Own Metadata, and What That Costs You

SuperPrompt is an attempt to engineer prompts that might help us understand AI agents.

6,431 stars566 forksUnknownLicense varies

At a glance

What is it?
SuperPrompt is a single XML prompt file, positioned as custom project instructions for Claude, that asks the model to generate a new metadata block for every request and then reason through a fixed set of named tags. It is a prompt-engineering artefact, not a library, and the README says so plainly.
Who is it for?
Adopt SuperPrompt if you want to read and edit a prompt file directly and you accept that the output will be uneven, including hallucinations the author acknowledges. Do not adopt it if you need reproducible agent behaviour, a stable API contract, or any guarantee about licence terms, because the repository metadata lists no licence and no primary language.
Can I use it commercially?
Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
Is it still maintained?
Activity is slowing. The repository last received commits 6 months ago.
What is it written in?
GitHub does not report a main language for this repository.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • NeoVertex1/SuperPrompt6,431 ★ · +3
Star history
Repository2026-09-112026-11-15
NeoVertex1/SuperPrompt6.4k6.4k

3 Stars in the last 65 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

What SuperPrompt is, and the specific gap it claims to fill

SuperPrompt is not a framework, a package or a service. The repository holds a prompt, written in XML, that the author intends you to paste into Claude as custom instructions in the project knowledge. The stated motivation is narrow: the author says the prompt took many months and is open sourced because it might help others understand AI agents. The README describes the result as a canonical holographic metadata, a phrase the author immediately concedes sounds absurd, and then offers a plainer description: the prompt turns logical statements into actionable LLM agents, starting as a basic XML agent and moving into what the README calls the model's tree-of-thought.

The audience is therefore people who already write prompts by hand and want a larger structure to work inside. It is not aimed at teams wiring an agent into a product. If you are looking for an orchestration layer, this is the wrong artefact. If you are looking for a long, opinionated prompt you can read in one sitting and modify, it is exactly that.

The mechanism: metadata that regenerates per request, then a fixed tag pipeline

Two things happen when the prompt runs. The first is the metadata block. The prompt ships with a default:

<prompt_metadata> Type: Universal Catalyst Purpose: Infinite Conceptual Evolution Paradigm: Metamorphic Abstract Reasoning Constraints: Self-Transcending Objective: current-goal </prompt_metadata>

The README calls these global instructions that adapt to any request. The example given is a user asking the model to think about a complex equation; the output metadata then reads Type: Mathematical Analysis, Purpose: Deep Exploration of Complex Equation, Constraints: Mathematical Rigor. The claim is that the model rewrites its own meta-prompt to fit the task because the prompt permits it.

The second part is the tag set that follows. The prompt defines an answer_operator function and instructs the model to state what it is going to do at the start of every answer. Inside answer_operator, the README's copy of the prompt opens with a claude_thoughts tag, the prompt_metadata block and a core tag written in binary.

The author singles out the think tag as the part that matters:

<think> ?(...) → !(...) </think>

The argument in the README is that other implementations use an empty thinking tag with no information inside it, and that the metadata is what makes this version different. That is the entire technical claim. The one piece of evidence offered is a screenshot committed to the repository.

Getting it running: there is no install step, only a paste

There is no package manager command, no build and no configuration file. The README says you will want to use this prompt with Claude as custom instructions in the project knowledge, and adds that it also works with other LLMs. In practice that means creating a Claude project, opening the project instructions field and pasting the XML block from the README, which begins with <rules> and META_PROMPT1 and continues through the tag definitions.

The only named interface is the model itself. The README shows a usage pattern rather than a command: a user prompt such as asking the model to use all its tags to think about a given equation. The expected response shape is the rewritten <prompt_metadata> block followed by reasoning through the tags. Because the prompt instructs the model to answer what it is going to do at the beginning of each response, the first line of output is a self-description.

Two practical notes follow from the repository layout. The README links to Readme_JP.md for a Japanese version of the documentation, so the explanation exists in two languages. And the README itself includes the line that the explanation will continue soon, which means the English documentation is explicitly incomplete. Anyone evaluating this should treat the prompt block as the primary source and the prose around it as partial commentary.

The failure mode the author names first: refusal and hallucination

The README is unusually direct about the downside. It states that the prompt can be considered a soft jailbreak and that many times Claude will deny the prompt. That is a real operational problem, not a footnote. If the model declines, you get no metadata block and no tag traversal, and the failure is not deterministic in a way you can catch programmatically without parsing the response.

The second admitted cost is output quality. The README says the ideas can be bad ideas or hallucinations, and that the best use is to try to get a novel point of view. That is an acceptable trade for brainstorming and an unacceptable one for anything where a wrong answer propagates. The author also pre-empts a common misreading: SuperPrompt is not a mystical prompt, and there is no intention to turn the model into a conscious being, even though the prompt mentions those things.

A third constraint is the absence of any versioning or evaluation harness. The README calls the project forever beta. With no published GitHub releases, a change to the prompt block is a change to behaviour with nothing to diff against except your own saved copies.

Where a plain custom instruction or a structured framework fits better

The obvious alternative for day-to-day work is a short custom instruction: a few sentences describing role, output format and constraints, pasted into the same project knowledge field. The difference in approach is that a short instruction constrains the model, while SuperPrompt expands the space the model is allowed to explore by handing it a vocabulary of abstract operations and letting it rewrite its own framing per request. If your task has a correct answer, the short instruction wins because it narrows the search. If your task is generating candidate framings for a problem you have not yet defined, the SuperPrompt approach at least attempts something the short instruction does not.

The other alternative is a code-level agent framework, where the loop, the tool calls and the retry logic live in your program rather than in a prompt. That gives you determinism, logging and version control over behaviour. SuperPrompt puts its control structure inside the model's context as prompt text, which means it is a suggestion the model may or may not follow. Those are not competing implementations of the same idea; they are different places to put control. The README's own framing, that this is aimed at the model rather than at humans and will therefore look like gibberish, is a fair description of the trade being made.

Maintenance, licensing and what the repository metadata does not tell you

The maintenance story is thin by construction. The repository has no releases, no listed primary language and no licence. The last push was on 2026-04-26, and there is no release cadence to plan against. Upgrading means re-reading the prompt block and re-pasting it into your project instructions, then accepting that any saved output you produced under the old block is no longer comparable.

The licence question is the one to resolve before anything else. With no licence identifier in the repository metadata, the default position under most jurisdictions is that the author retains rights, which means redistribution or bundling the prompt into a product is not clearly permitted. That is a factual statement about the metadata, not legal advice; read the repository's own licence file, if one exists, and decide with whoever handles that for you. The same applies to the Japanese README: it is documentation, and its terms travel with the repository.

One more thing worth verifying before you invest time: confirm that the prompt block in the README is the current one. The project describes itself as forever beta.

Editorial conclusion

Adopt SuperPrompt if you want to read and edit a prompt file directly and you accept that the output will be uneven, including hallucinations the author acknowledges. Do not adopt it if you need reproducible agent behaviour, a stable API contract, or any guarantee about licence terms, because the repository metadata lists no licence and no primary language. Before using it in anything you ship, open the repository and confirm the licence file, the current contents of the prompt block and the Readme_JP.md translation, since the English README states the explanation is unfinished and the project describes itself as forever beta.

Frequently asked questions

What is a superprompt, and what does NeoVertex1/SuperPrompt actually contain?

It is one author's prompt, worked on for many months, that steers a model with XML-style tags and a five-field prompt_metadata block the model rewrites per task. The repository holds twelve top-level entries: ten markdown files, one image and a research directory. There is no package and no release.

Is SuperPrompt a prompt library or an installable tool?

Neither. The repository ships markdown prompt files and one image, with no package manifest, no stated licence and no GitHub releases, so there is nothing to install and nothing to depend on. The author says to use the prompt with Claude as custom instructions in the project knowledge.

What does an example SuperPrompt run look like?

The single worked example asks the model to think about Φ(z,s,t) = z^s · exp(i · t · log(1 + |z|^2)), and the reply begins with a retyped metadata block: Type becomes Mathematical Analysis, Constraints becomes Mathematical Rigor, and Objective becomes Comprehensive understanding and interpretation of the given equation.

Does SuperPrompt include a version for ChatGPT?

One top-level file is named prompt_for_gpt.md, and another is alternative_prompt.md. The README does not describe what changes between them or how the GPT version differs from the Claude-oriented one.

Official sources

  1. Issues
  2. NeoVertex1/SuperPrompt on GitHub
  3. README

Was this useful?