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.
Borrowing it
Nothing to install: this file belongs to nteract/semiotic. 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/nteract/semiotic/main/AGENTS.mdgit 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/instructions/nteract/semiotic/agents-md)<a href="https://agentmods.dev/instructions/nteract/semiotic/agents-md"><img src="https://agentmods.dev/badge/instructions/nteract/semiotic/agents-md/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/instructions/nteract/semiotic/agents-md"><img src="https://agentmods.dev/badge/instructions/nteract/semiotic/agents-md.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.01424 | $0.01424 |
| Opus 5.5 | $0.00570 | $0.00570 |
| Sonnet 5.5 | $0.00285 | $0.00285 |
| Haiku 4.5 | $0.00142 | $0.00142 |
Grade A, and why
semiotic 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 1mo 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Semiotic repository instructions
Scope
Semiotic is a TypeScript/React data-visualization library with high-level chart components, lower-level Stream Frames, browser and server renderers, a Vite documentation site, and schema-backed AI/MCP tooling.
Keep this file focused on instructions that apply to most repository work. Use the task-specific sources below instead of loading large references by default.
Source map
CONTRIBUTING.md: complete development workflow, architecture, and command reference.ai/system-prompt.md: compact product/API guidance for generating Semiotic chart code.ai/reference.md: comprehensive Semiotic product reference; consult only the relevant section.ai/schema.json: machine-readable component and prop schemas.ai/behaviorContracts.cjs: canonical agent-visible behavior rules.ai/examples.md: on-demand examples; search for the relevant chart or task rather than loading the whole file.agent-skill/semiotic-charts/SKILL.md: portable chart-authoring and validation workflow shipped with the package..agents/skills/blog-post/: the shared blog-authoring workflow and templates.
When documentation disagrees with runtime code, generated chart specs, or tests, treat the executable source as authoritative and update the docs and generated artifacts in the same change.
Repository layout
src/components/charts/: high-level chart components by family.src/components/stream/: retained scene, canvas/SVG, interaction, streaming, and worker infrastructure.src/components/{ai,server,recipes,data}/: intelligence, static rendering, custom-layout recipes, and transforms.ai/: schemas, MCP server, CLI, prompts, contracts, and examples.docs/: Vite documentation application and examples.integration-tests/: Playwright browser and visual coverage.scripts/: build, generation, validation, and release tooling.
Working agreements
- Preserve unrelated worktree changes. Make the smallest coherent change and review the final diff.
- Prefer TypeScript for new source files. The project uses strict TypeScript, double quotes, no semicolons, Prettier, and ESLint.
- Prefer high-level chart components for public examples. Use Stream Frames only when the high-level API does not expose the required control.
- Prefer family subpath imports (
semiotic/xy,semiotic/network, and so on) in production examples. Avoid widening entry graphs accidentally. - Preserve public API compatibility unless the task explicitly authorizes a breaking change. Update types, chart specs, schemas, docs, and tests together.
- Add or update focused tests for behavior changes. Do not weaken assertions or raise bundle/coverage limits merely to make a check pass.
- For interactive examples, hover real marks and interactive edges in a browser
and assert useful tooltip content, placement after zoom/pan/resize, and dismissal.
Do not silently disable tooltips to avoid a defect; an inspector or mount-only
test does not verify hover behavior. See
ai/behaviorContracts.cjsfor callback datum shapes and the disabled/empty tooltip contract. - For a confirmed, user-visible defect—not a transient CI or infrastructure failure—perform a related-surface audit before closing it. Check equivalent renderers, entry points, generated artifacts, formats, and public API paths; fix or cover any same-class issue found, and record the audit scope and result with verification.
- Do not hand-edit
dist/,docs/build/, generated manifests, or generated sections between marker comments. Run the owning generator. - Do not add production dependencies, change lockfiles, publish packages, push branches, or deploy without explicit task scope.
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.
- 1mo ago Changed · +5 lines · +82 tokens per session 8d0305c0e609
- 2mo ago First seen · 116 lines · 1,342 tokens per session scan A 49431f184f84
semiotic AGENTS.md is an instructions file published in the GitHub repository nteract/semiotic (2,717 stars, last pushed today), licensed Apache-2.0. It adds 1,424 tokens to every session, about $0.0057 per session on Opus 5.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
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.