Borrowing it
Nothing to install: this file belongs to hetpatel-11/supermemory-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hetpatel-11/supermemory-mcp/main/.agent/skills/chatgpt-app-builder/SKILL.mdgit clone --depth 1 https://github.com/hetpatel-11/supermemory-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/hetpatel-11/supermemory-mcp/chatgpt-app-builder)<a href="https://agentmods.dev/skills/hetpatel-11/supermemory-mcp/chatgpt-app-builder"><img src="https://agentmods.dev/badge/skills/hetpatel-11/supermemory-mcp/chatgpt-app-builder/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hetpatel-11/supermemory-mcp/chatgpt-app-builder"><img src="https://agentmods.dev/badge/skills/hetpatel-11/supermemory-mcp/chatgpt-app-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00129 | $0.00752 |
| Opus 5 | $0.00064 | $0.00376 |
| Sonnet 5 | $0.00026 | $0.00150 |
| Haiku 4.5 | $0.00013 | $0.00075 |
Grade A, and why
chatgpt-app-builder scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to chatgpt-app-builder — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ChatGPT App Builder
Build ChatGPT apps with interactive widgets using mcp-use. Zero-config widget development with automatic registration and built-in React hooks.
The app is consumed by two users at once: the human and the ChatGPT LLM. They collaborate through the widget -- the human interacts with it, the LLM sees its state. The widget is your shared surface.
Before You Code
- Clarify what to build → discover.md: when starting a new app, validating an idea, or scoping features
- Design tools and widgets → architecture.md: when deciding what needs UI vs tools-only, designing UX flows
Setup
- Scaffold and run → setup.md: when creating a new project, starting dev server, connecting to ChatGPT/Claude
Implementation
- Server handlers + widget creation → server-and-widgets.md: when writing server.tool() with widgets, widget() helper, React widget files
- Widget state and LLM context → state-and-context.md: when persisting state, triggering LLM from widget, managing ephemeral vs persistent data
- Display modes, theme, layout → ui-guidelines.md: when adapting to inline/fullscreen/PiP, handling theme, device, locale
- Component API → components-api.md: when using McpUseProvider, Image, ErrorBoundary, useWidget
- CSP and metadata → csp-and-metadata.md: when configuring external domains, dual-protocol metadata
- Advanced patterns → widget-patterns.md: when building complex widgets with tool calls, state, theming
Quick Reference
// Server
import { MCPServer, widget, text, object } from "mcp-use/server";
server.tool({ name: "...", schema: z.object({...}), widget: { name: "widget-name" } },
async (input) => widget({ props: {...}, output: text("...") })
);
// Widget (resources/widget-name.tsx)
import { McpUseProvider, useWidget, type WidgetMetadata } from "mcp-use/react";
export const widgetMetadata: WidgetMetadata = { description: "...", props: z.object({...}) };
export default function MyWidget() {
const { props, isPending, callTool, sendFollowUpMessage, state, setState, theme } = useWidget();
if (isPending) return <McpUseProvider autoSize><div>Loading...</div></McpUseProvider>;
return <McpUseProvider autoSize><div>{/* UI */}</div></McpUseProvider>;
}
What ships with it
17 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- evals/architecture.json 2.3 KB
- evals/discover.json 1.7 KB
- evals/README.md 476 B
- evals/skill.json 2.1 KB
- evals/state-and-context.json 1.4 KB
- evals/ui-guidelines.json 1.6 KB
- evals/widgets.json 1.6 KB
- LICENSE.txt 8.9 KB
- references/architecture.md 5.0 KB
- references/components-api.md 8.3 KB
- references/csp-and-metadata.md 5.1 KB
- references/discover.md 2.1 KB
- references/server-and-widgets.md 6.3 KB
- references/setup.md 2.1 KB
- references/state-and-context.md 6.6 KB
- references/ui-guidelines.md 5.1 KB
- references/widget-patterns.md 6.6 KB
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 56 lines · 129 tokens per session scan A 7b8992f5fc17
chatgpt-app-builder is a skill published in the GitHub repository hetpatel-11/supermemory-mcp (1 stars, last pushed 6mo ago), licensed MIT. It adds 129 tokens to every session and 752 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to chatgpt-app-builder, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…