Semiotic is a React library for building data visualizations such as charts, network graphs, streaming displays, and coordinated dashboards. It is used by developers who need to render data-driven interfaces, including with AI coding assistants. Its schemas and MCP server support the catalogue's add-ons for generating chart code.
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 nteract/semiotic --skill chatgpt-app-submissiongit clone --depth 1 https://github.com/nteract/semioticWrote 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/nteract/semiotic/chatgpt-app-submission)<a href="https://agentmods.dev/skills/nteract/semiotic/chatgpt-app-submission"><img src="https://agentmods.dev/badge/skills/nteract/semiotic/chatgpt-app-submission/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/nteract/semiotic/chatgpt-app-submission"><img src="https://agentmods.dev/badge/skills/nteract/semiotic/chatgpt-app-submission.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00056 | $0.02309 |
| Opus 5 | $0.00028 | $0.01154 |
| Sonnet 5 | $0.00011 | $0.00462 |
| Haiku 4.5 | $0.00006 | $0.00231 |
Grade A, and why
chatgpt-app-submission 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 10d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- chatgpt-app-submission — 88% identical, 30 lines differ
How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ChatGPT App Submission
Use this skill when a developer needs a chatgpt-app-submission.json file for a ChatGPT Apps submission. The file is uploaded in the Apps submission form to fill out parts of App Info, MCP Server, and Testing.
Workflow
- Inspect the MCP server codebase from the current working directory.
- Read repo metadata, package metadata, README files, app manifests, tool descriptors, resource templates, and widget metadata needed to understand the app.
- Find every exposed MCP tool, its declared
readOnlyHint,openWorldHint, anddestructiveHintannotations, and whether it declaresoutputSchema. - Read each tool implementation and any called helper functions needed to understand side effects.
- Compare tool annotations, tool names, tool descriptions, and CSP values against actual behavior. If any value is missing, stale, misleading, or inconsistent, ask the developer for approval before updating source.
- Generate concise review-facing app info suggestions, tool hint justifications, positive test cases, and negative test cases.
- Write
chatgpt-app-submission.jsonin the current working directory. - Print review-check findings and any missing
outputSchemawarnings in the final response, and explain what the developer should do with each finding before submission.
Do not infer behavior from the tool name alone. Use the real tool implementation and declared annotations. If a tool calls into another module or API client, inspect enough of that path to know whether it reads, writes, deletes, sends, publishes, or changes external state.
App Info Rules
Suggest app info from source-of-truth project metadata and the tool behavior you inspected. Keep it plain-language and submission-review-facing.
display_name: use the product or app name from repo metadata, package metadata, README, manifest, or existing configuration. Keep it short enough for the submission form.subtitle: summarize what the app does in one short functional phrase, not marketing copy. It must be 30 characters or less.description: describe concrete user value and the main workflows the tools support.category: choose one ofBUSINESS,COLLABORATION,DESIGN,DEVELOPER_TOOLS,EDUCATION,ENTERTAINMENT,FINANCE,FOOD,LIFESTYLE,NEWS,PRODUCTIVITY,SHOPPING, orTRAVEL.
What ships with it
1 file 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.
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.
- 10d ago First seen · 157 lines · 56 tokens per session scan A c9b43ca8fe60
chatgpt-app-submission is a skill published in the GitHub repository nteract/semiotic (2,705 stars, last pushed yesterday), licensed Apache-2.0. It adds 56 tokens to every session and 2,309 once invoked, about $0.0003 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 skills, from other repositories
example
Create new example charts for Recharts documentation website.
commit
Create git commits in the Unovis repo that pass its commitlint rules. Unovis uses a CUSTOM commit format (Type | Scope | Subscope: Sentence-case subject), NOT Conventional Commits, so feat:/fix: will be rejected by the commit-msg hook. Use this whenever staging and committing changes, writing or rewriting a commit…
add-component
Add a new visualization component to Unovis end to end — the TypeScript core, the shared registry, the generated framework wrappers, a dev example, a gallery example, and docs. Use when asked to add/create a new component, chart type, plot, or diagram to the library, or to wire an existing core component through to…
add-gallery-example
Add an example to the Unovis gallery — a per-framework example directory under packages/shared/examples, registered in examples-list.tsx, with light/dark previews. Use when asked to add a gallery example, showcase a chart in the gallery, or create the gallery entry that accompanies a new component.
open-pr
Open a pull request for the Unovis repo with the project's conventions — correct branch off main, the standard commit grouping, and the checklist-style PR body used by the maintainers. Use when asked to open/create/submit a pull request, prepare a branch for review, or write a PR description in this repository.
infographic-item-creator
Generate or update infographic Item components for this repo (TypeScript/TSX in src/designs/items). Use when asked to design, implement, or modify data item visuals, layout logic, or registerItem composites.