TokenEconomizer
Experience-Driven Black-Box Cost Control for Coding Agents
Reverse engineer a GitHub repo or a website into a prompt you can build from.
Developer toolsTypeScript · PLpgSQLGitHub @filiksyosOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Reverse engineer any repo into it's original prompt
Translation pending
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
Turn a public GitHub repository into a single synthetic user prompt that someone might paste into Cursor, Claude Code, Codex, etc. to vibe code the project from scratch.
The app pulls repo metadata, a root file tree (depth 1), and the README, then uses an LLM to produce one short, conversational prompt grounded in that context.
Paste a GitHub URL or owner/repo on the home page. You can also open /owner/repo (e.g. /vercel/next.js) for a shareable link that runs the same flow.Read the full README ↗https://github.com/user-attachments/assets/f0cdb7b2-c6f0-4483-8a01-153170479f2e
Turn a public GitHub repository into a single synthetic user prompt that someone might paste into Cursor, Claude Code, Codex, etc. to vibe code the project from scratch.
The app pulls repo metadata, a root file tree (depth 1), and the README, then uses an LLM to produce one short, conversational prompt grounded in that context.
Paste a GitHub URL or owner/repo on the home page. You can also open /owner/repo (e.g. /vercel/next.js) for a shareable link that runs the same flow.
GitHub-style /owner/repo/tree/... URLs on this site redirect to /owner/repo so they do not 404. The reverse flow still uses the whole repo for now; subfolder-aware context (scoped to that path) is planned for a later change.
Next.js 16 (App Router), React 19, TypeScript, Tailwind CSS 4, GitHub API, Supabase (optional), Stripe (optional).
Copy .env.example to .env.local and fill in at least one LLM API key.
The quick reverse endpoint supports five providers. Set GITREVERSE_QUICK_LLM to pin one, or leave it unset (auto) to let the app use whichever key it finds first:
| Provider | Key env var | Model env var | Default model |
|---|---|---|---|
| Grok (xAI) | XAI_API_KEY | XAI_MODEL | grok-3 |
| OpenRouter | OPENROUTER_API_KEY | OPENROUTER_MODEL | google/gemini-2.5-pro |
| Azure OpenAI | AZURE_OPENAI_API_KEY + AZURE_OPENAI_BASE_URL | AZURE_OPENAI_MODEL | gpt-5.4 |
| Google AI Studio | GOOGLE_GENERATIVE_AI_API_KEY | GOOGLE_AI_STUDIO_MODEL | gemini-2.5-pro |
| ApiSmart | APISMART_API_KEY | APISMART_MODEL | DEEPSEEK_V4_FLASH |
In auto mode the order of preference is: Grok → OpenRouter → Azure → Google → ApiSmart.
ApiSmart (sponsored) is an OpenAI-compatible gateway. Copy the exact Model ID from the ApiSmart models page (IDs differ from display names). Pin it with GITREVERSE_QUICK_LLM=apismart.
Azure quick reverse uses gpt-5.4 by default with AZURE_OPENAI_REASONING_EFFORT=medium. Title generation also uses Azure and defaults to gpt-5.4-mini with reasoning disabled.
Prompt-cache embeddings and /library hybrid search now use Azure embeddings first:
AZURE_OPENAI_EMBEDDING_MODEL — defaults to text-embedding-3-smallAZURE_OPENAI_EMBEDDING_DIMENSIONS — defaults to 512AZURE_OPENAI_EMBEDDING_DEPLOYMENT — optional explicit deployment nameAZURE_OPENAI_DEPLOYMENT_NAME_MAP — optional model=deployment mapping when deployment names differ from model idsIf your Azure resource does not yet have an embedding deployment, you can temporarily set OPENAI_API_KEY as an embedding-only fallback while quick reverse and title generation stay on Azure.
GITHUB_TOKEN — optional; increases GitHub API rate limits.SUPABASE_URL + SUPABASE_PUBLISHABLE_KEY — optional; enables server-side caching of quick prompts in prompt_cache and exposes the /library page.VIEWS_IP_SALT — required in production. Generate one with openssl rand -hex 32. The app will refuse to start in production without a non-default value.| Path | Description |
|---|---|
/ | Home — quick reverse (codebase or website) |
/library | Browse cached quick prompts (requires Supabase) |
/history | Your prompt history (profile menu when signed in; syncs to Supabase) |
/[owner]/[repo] | Shareable quick-reverse link |
/[owner]/[repo]/tree/... | Redirects to /[owner]/[repo] |
pnpm install
pnpm dev
Open http://localhost:3000.
pnpm build
pnpm start
pnpm lint
pnpm test:library
test:library runs credential-free regression tests for library filtering, source fallbacks, and outage handling.
GitReverse's source code is licensed under the MIT License.
Third-party dependencies and assets retain their respective licenses and rights. See the sponsor asset sources for the existing brand-asset notices.