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 instructions/alignbase/sunpeak/agents-mdgit clone --depth 1 https://github.com/Alignbase/sunpeakWhat 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.08763 | $0.08763 |
| Opus 5 | $0.04381 | $0.04381 |
| Sonnet 5 | $0.01753 | $0.01753 |
| Haiku 4.5 | $0.00876 | $0.00876 |
Grade A, and why
sunpeak AGENTS.md 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 yesterday.
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 — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sunpeak
Note that "sunpeak", except where required in URLs or code, is always lowercase.
sunpeak is a framework for building MCP Apps with interactive UIs that run inside AI chat hosts (ChatGPT, Claude, and future major hosts). Built on top of the MCP Apps SDK (@modelcontextprotocol/ext-apps).
ChatGPT apps are now submitted and published as plugins. The app portion is still based on MCP Apps or the OpenAI Apps SDK, so sunpeak's protocol and runtime architecture do not change. Adding a custom app requires ChatGPT Developer mode, enabled from the bottom-left user menu under Settings > Security and login > Developer mode. Local developer-mode apps are then created from the ChatGPT homepage under Plugins > +, while public apps are submitted as MCP-backed plugins through the OpenAI Platform.
The value proposition of the sunpeak framework is to help developers and their agents:
- Test MCP Apps locally and automatically (in CI/CD) using a replica of the ChatGPT and Claude runtimes.
- Save time manually testing all possible host, server, app, ui, and backend states.
- Protect developers from 4-click manual refreshes on every code change in each host.
- Cancel all the $20 per person per host per month testing accounts.
- Avoid burning host credits on every test and code change.
- Verify MCP tools work across multiple LLM models via the eval framework. Evals connect to the MCP server, discover tools, and send prompts to multiple models (GPT-4o, GPT-4o-mini, o4-mini, Claude Sonnet, Gemini 2.0 Flash) via the Vercel AI SDK. Cases can include App Context for follow-up turns that depend on model-visible UI state. Each case runs N times per model and reports pass/fail counts, so developers can confirm that tool descriptions, schemas, and App Context work reliably on smaller and cheaper models. Opt-in via
sunpeak test --evalbecause evals cost money. - Automate the real-host testing loop with live tests (
sunpeak test --live): scripts that drive a real browser into ChatGPT (and other hosts as they're supported), send prompts that trigger MCP tool calls against the developer's server, and assert against the actually-rendered app via Playwright. Live tests catch what the inspector can't (real MCP connection behavior, real LLM tool invocation, host-specific iframe rendering, production resource loading) and replace the manual prompt-and-click loop. Opt-in because they hit real accounts. - Build multi-platform MCP Apps in a structured way that's easy to understand and get started.
- Test their MCPs in ChatGPT with HMR and Claude with automatic rebuilds and refresh notifications.
- Embed the Inspector as a React component inside any third-party React app to render arbitrary MCP Apps. The
<Inspector app={...} onCallTool={...} />shape exposes the same double-iframe runtime, host shells, and conversation chrome as the CLI inspector, but without any sunpeak-owned servers or/__sunpeak/*runtime dependencies. Tool calls flow through a callback the embedder owns; resource HTML is passed as a string. Embedders host the static sandbox proxy (dist/sandbox-proxy.html) on a separate origin from their own app — or fall back to the same-originsrcdocvariant for zero deployment. This is a first-class use case; treat it as load-bearing when designing changes.
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.
- yesterday First seen · 348 lines · 8,763 tokens per session scan A f6ebca83aba0
sunpeak AGENTS.md is an instructions file published in the GitHub repository Alignbase/sunpeak (214 stars, last pushed 3d ago), licensed MIT. It adds 8,763 tokens to every session, about $0.0438 per session on Opus 5. 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 instructions, from other repositories
jesse AGENTS.md
Instructions for jesse-ai/jesse, covering jesse repository guide for ai agents, skills, key characteristics, central framework and technology stack.
laravel AGENTS.md
AGENTS.md instructions for laravel/laravel, covering laravel application, prerequisites and agent setup.
AgentEval copilot-instructions.md
Instructions for AgentEvalHQ/AgentEval, covering agenteval - ai coding agent instructions, architecture overview, environment setup, optional: secondary models for comparison and build & test commands.
LarAgent AGENTS.md
Instructions for MaestroError/LarAgent, covering purpose, key principles, planning, executing plan and testing.
AgentEval tracing.instructions.md
Guidelines for implementing trace recording and replay.
zhin zhin-plugin.instructions.md
Instructions for zhinjs/zhin, covering zhin plugin runtime authoring, package contract, convention directories, imports and native typescript and command routes.