agentviz copilot-instructions.md

Project instructions for AGENTVIZ, a React and Vite application that replays and visualizes AI-agent sessions. They define its technology, commands, naming, design, testing, and documentation rules.

In plain words
What is it for?
Use them when modifying AGENTVIZ components, styles, parsers, tests, build settings, or documentation, particularly for changes that must update its five synchronized project artifacts.
Why use it?
They give a coding agent the project’s working rules, reducing inconsistent edits, missed tests, incorrect product naming, and documentation that falls out of sync with code changes.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/jayparikh/agentviz/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/jayparikh/agentviz

Made for: GitHub Copilot.

Per session 1,103 This file is loaded in full into every session.
When invoked 1,103 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01103 $0.01103
Opus 5 $0.00551 $0.00551
Sonnet 5 $0.00221 $0.00221
Haiku 4.5 $0.00110 $0.00110

Measured 2d ago against content hash e69530120edb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

agentviz copilot-instructions.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 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.

.github/copilot-instructions.md · 74 lines

How it starts

The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTVIZ

Session replay visualizer for AI agent workflows (Claude Code, VS Code Copilot Chat, Copilot CLI).

Stack

  • React 18 + Vite 6, inline styles only, JetBrains Mono font
  • Mixed JS/TS: components and hooks are plain JSX, parsers and data libs are TypeScript
  • Design tokens in src/lib/theme.js

Commands

npm run dev          # Dev server
npm run build        # Production build to dist/
npm test             # Run tests via Vitest
npm run test:watch   # Watch mode
npm run typecheck    # tsc --noEmit

Rules

  • Search existing code before writing new abstractions.
  • Run tests after every non-trivial change.
  • Prefer editing existing files over creating new ones.
  • Never silently apply config changes — surface drafts first.
  • Product name is always AGENTVIZ (all caps, no spaces). Never "AgentViz" or "Agentviz".
  • All UI changes must conform to docs/ui-ux-style-guide.md. Review the checklist at the bottom of that file before approving any PR that touches components, styles, or visual behavior.

Five-Artifact Sync Rule

Every UI change must update ALL FIVE of these before committing. Never let them drift:

  1. README.md — feature descriptions, architecture section, file tree
  2. docs/ui-ux-style-guide.md — token values, patterns, rules
  3. docs/color-palette.html — visual swatch reference; hex values must match theme.js and the style guide
  4. docs/screenshots/ — all 8 screenshots (see Screenshots section below)
  5. Repo memory — store any new conventions with store_memory

Screenshots

The README references 8 screenshot files in docs/screenshots/. All must be kept in sync.

Files: landing.png, session-hero.png, replay-view.png, tracks-view.png, waterfall-view.png, graph-view.png, stats-view.png, coach-view.png

Workflow (using Playwright MCP tools):

  1. Start dev server: npm run dev
  2. Navigate to http://127.0.0.1:3000, resize to 1400x860
  3. Capture landing.png from the landing page (before loading a session)
  4. Click "Load a demo session", then click each tab and capture: replay, tracks, waterfall, graph, stats
  5. For Coach: click the tab, hide the error banner with JS before capturing:
    document.querySelectorAll('*').forEach(el => {
      if (el.children.length === 0 && el.textContent.trim().startsWith('AI analysis failed')) {
        let n = el;
        for (let i = 0; i < 6; i++) {
          if (n.parentElement?.textContent.trim().startsWith('AI analysis failed')) n = n.parentElement;
          else break;
        }
        n.style.display = 'none';
      }
    });
    
  6. Copy replay-view.png to session-hero.png (hero reuses replay image)

Read the full file on GitHub · 74 lines

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.

  1. 2d ago First seen · 74 lines · 1,103 tokens per session scan A e69530120edb

Subscribe to this mod's changes

agentviz copilot-instructions.md is an instructions file published in the GitHub repository jayparikh/agentviz (95 stars, last pushed 3d ago), licensed MIT. It adds 1,103 tokens to every session, about $0.0055 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.

Related

Other instructions, from other repositories

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

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).

microsoft/vscode · 6,785 tokens

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.

langchain-ai/langchain · 4,345 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens