Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/imoonkey/openweb/chatgptnpx skills add imoonkey/openweb --skill chatgptgit clone --depth 1 https://github.com/imoonkey/openwebWhat 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 | $0.00000 | $0.00691 |
| Opus 5 | $0.00000 | $0.00345 |
| Sonnet 5 | $0.00000 | $0.00138 |
| Haiku 4.5 | $0.00000 | $0.00069 |
Grade A, and why
chatgpt 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ChatGPT
Overview
ChatGPT backend API — OpenAI's conversational AI interface. Content platform archetype.
Workflows
Browse conversations
listConversations→ pick conversation →conversationIdgetConversation(conversationId)→ full message tree
Search and read
searchConversations(query)→ results withconversationIdgetConversation(conversationId)→ full message tree
Send a message
sendMessage({ prompt })→ SPA-driven send →{ conversation_id, response_text }getConversation(conversation_id)→ full message tree once the reply finishes
sendMessage no longer needs model / parentMessageId — the chatgpt-web
adapter drives the live SPA, so the page picks the active model and threads
the new turn for you. Pass prompt only.
Operations
| Operation | Intent | Key Input | Key Output | Notes |
|---|---|---|---|---|
| getProfile | authenticated user info | — | id, name, email | entry point |
| listConversations | recent conversations | limit?, cursor? | items[].id, title, cursor | paginated (cursor) |
| getConversation | full conversation detail | conversationId ← listConversations | sendMessage | mapping (message tree), current_node | tree structure |
| searchConversations | search past conversations | query | items[].conversation_id, snippet | paginated (offset cursor) |
| getModels | available models | — | models[].slug, title | entry point |
| sendMessage | send message, get reply | prompt | conversation_id, response_text, sse_event_count | WRITE; SPA-driven adapter |
Quick Start
# Get user profile
openweb chatgpt exec getProfile '{}'
# List recent conversations
openweb chatgpt exec listConversations '{"limit": 10}'
# Get a conversation
openweb chatgpt exec getConversation '{"conversationId": "<id>"}'
# Search conversations
openweb chatgpt exec searchConversations '{"query": "python"}'
# Get available models
openweb chatgpt exec getModels '{}'
# Send a message (SPA-driven)
openweb chatgpt exec sendMessage '{"prompt": "Summarize the OpenWeb readme."}'
What ships with it
13 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.
- adapters/chatgpt-api.ts 5.1 KB runs code
- adapters/chatgpt-web.ts 5.0 KB runs code
- DOC.md 7.3 KB
- examples/getConversation.example.json 303 B
- examples/getModels.example.json 224 B
- examples/getProfile.example.json 225 B
- examples/listConversations.example.json 286 B
- examples/searchConversations.example.json 267 B
- examples/sendMessage.example.json 280 B
- manifest.json 512 B
- openapi.yaml 16 KB
- pipeline-gaps.md 2.1 KB
- PROGRESS.md 5.3 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.
- 2d ago First seen · 71 lines · 0 tokens per session scan A b6c996a87464
chatgpt is a skill published in the GitHub repository imoonkey/openweb (58 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 691 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.