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 skills add tambo-labs/charming-mcp --skill charminggit clone --depth 1 https://github.com/tambo-labs/charming-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/tambo-labs/charming-mcp/charming)<a href="https://agentmods.dev/skills/tambo-labs/charming-mcp/charming"><img src="https://agentmods.dev/badge/skills/tambo-labs/charming-mcp/charming/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/tambo-labs/charming-mcp/charming"><img src="https://agentmods.dev/badge/skills/tambo-labs/charming-mcp/charming.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.00045 | $0.02598 |
| Opus 5 | $0.00023 | $0.01299 |
| Sonnet 5 | $0.00009 | $0.00520 |
| Haiku 4.5 | $0.00005 | $0.00260 |
Grade A, and why
charming scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
When Charming MCP tools are available, build with the tools directly. Do not use `curl`, `fetch`, shell HTTP calls, or the raw HTTP API for app creation. This is a copy
98% identical to charming — 2 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Charming
Overview
Use this skill when the user asks to create an app with Charming, edit an existing Charming app, connect the Charming MCP server, or inspect Charming-generated app source.
Charming is a hosted service that generates, hosts, and updates small interactive web apps. Each app gets a real URL, persistent storage, and inline rendering inside MCP Apps-capable chat clients. It has two authoring paths:
- MCP tools (preferred): use this path whenever Charming tools such as
create_app,update_app,list_apps, orget_appare available to you. - HTTP API (fallback): use only when Charming MCP tools are not available and you have outbound HTTP access.
Connect
Charming is a remote server; there is nothing to clone, build, or run locally. Add the endpoint to your client's MCP settings:
| Client | Endpoint |
|---|---|
| Claude, Claude Code, Cursor, Codex, Gemini CLI, and most MCP clients | https://charm.ing/mcp |
| ChatGPT | the Charming listing in the ChatGPT Apps directory is one click; https://charm.ing/mcp/chatgpt is the Developer Mode fallback |
Charming's MCP endpoints always require a bearer token. OAuth with Dynamic Client Registration bootstraps one automatically on first connect: clients that support it show a one-time consent screen, with no API key to paste. Anonymous creation with no token is available on the HTTP path only (POST https://charm.ing/app), and an unclaimed app has a 7-day TTL until someone claims it. To mint a token by hand, use device pairing: POST https://charm.ing/api/pair/start, then poll. Full auth guide: usecharming.com/auth.md. Per-client paste-strings and setup steps: usecharming.com/clients.txt.
MCP workflow
When Charming MCP tools are available, build with the tools directly. Do not use curl, fetch, shell HTTP calls, or the raw HTTP API for app creation.
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.
- 8d ago First seen · 139 lines · 45 tokens per session scan A fba9c137eaeb
charming is a skill published in the GitHub repository tambo-labs/charming-mcp (1 stars, last pushed 17d ago), licensed MIT. It adds 45 tokens to every session and 2,598 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 98% identical to charming, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
a11y-debugging
Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
json-render-ui
Generate guardrailed UI from natural language. Emits constrained JSON that a Preact runtime renders. Use when the request is for a dashboard with metrics, charts, or tables; an admin panel; a data visualization interface; or a form-based application.
mapping-webapp
Generate behavioral/feature documentation for web apps using code-first analysis. Reads source code via tree-sitting to produce FEATURES.md, with optional visual verification via browser automation. Companion to tree-sitting. Use when documenting app behavior, creating feature inventories, generating behavioral ground…
reddit-search-api
Pure API reference for reddapi.dev - authentication, all endpoints (vector search, semantic search, trends, subreddit lookup), request parameters, response schemas, and error codes, with no research-workflow framing. Use when the user wants raw endpoint documentation, is debugging a reddapi.dev integration, needs…
domscribe
Work with Domscribe — the pixel-to-code bridge. Use when setting up, initializing, or configuring Domscribe for a project, OR when editing or modifying UI components (React, Vue, Next.js, Nuxt), implementing features from captured UI annotations, querying runtime context for source locations, exploring component…