What is PlanVisualizer AGENTS.md?

A set of project instructions for PlanVisualizer that tells AI coding agents how to start work, plan changes, connect parts, and build the project. It applies across different AI coding assistants.

Starting agent sessions, creating or checking project files, defining the project constitution, and following the project's blueprint, connection, and architecture phases.

It gives agents a shared way to work before they change code. This reduces missing files, unclear project rules, and disconnected implementation steps.

How ksyed0/PlanVisualizer configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to ksyed0/PlanVisualizer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/ksyed0/PlanVisualizer/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/ksyed0/PlanVisualizer

Made for: Codex, OpenCode.

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

README.md

[![agentmods](https://agentmods.dev/badge/instructions/ksyed0/planvisualizer/agents-md/github.svg)](https://agentmods.dev/instructions/ksyed0/planvisualizer/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/ksyed0/planvisualizer/agents-md"><img src="https://agentmods.dev/badge/instructions/ksyed0/planvisualizer/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/ksyed0/planvisualizer/agents-md"><img src="https://agentmods.dev/badge/instructions/ksyed0/planvisualizer/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 8,993 This file is loaded in full into every session.

When invoked 8,993 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.08993	$0.08993
Opus 5.5	$0.03597	$0.03597
Sonnet 5.5	$0.01799	$0.01799
Haiku 4.5	$0.00899	$0.00899

Measured 2mo ago against content hash b09e75651b31, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

PlanVisualizer 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 2mo 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.

AGENTS.md · 731 lines

How it starts

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

AGENTS.md — AI Agent Operating Standards

This file defines the operational principles, architecture, and collaboration standards for all AI agents working on this project. It is platform-agnostic and applies equally whether the agent is Claude (Anthropic), Gemini (Google), OpenCode, or any other AI coding assistant. Read this file in full at the start of every session, before any code is written or tools are built.

Platform note: This file is named AGENTS.md universally. The companion project constitution file is named PROJECT.md regardless of platform. If your AI tool requires a platform-specific filename (e.g., gemini.md for Antigravity, CLAUDE.md for Claude Code), create a symlink or copy pointing to PROJECT.md — do not maintain separate content.

🟢 Protocol 0: Initialization (Mandatory)

Before any code is written or tools are built:

Verify all project files exist — Create any that are missing. The full file list and purpose of each is defined in the 📂 File & Deliverable Structure table at the end of this document.
Initialize PROJECT.md — Ensure the Project Constitution is populated with data schemas, behavioral rules, architectural invariants, user profile (§5), and design system (§6).
Halt Execution — No code or scripts may be written until:

All Discovery Questions in PROJECT.md are answered (see Phase 1)
The Data Schema in PROJECT.md is confirmed
task_plan.md has an approved Blueprint

🏗️ Phase 1: B — Blueprint (Vision & Logic)

Discovery: At project start, ask the user the following 5 questions:

North Star: What is the singular desired outcome?
Integrations: Which external services are needed? Are credentials ready?
Source of Truth: Where does the primary data live?
Delivery Payload: How and where should the final result be delivered?
Behavioral Rules: How should the system act? (tone, logic constraints, “Do Not” rules)

Data-First Rule: Define the JSON Data Schema (input/output shapes) before any coding begins. Coding only starts once the payload shape is confirmed.

Read the full file on GitHub · 731 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.

2mo ago First seen · 731 lines · 8,993 tokens per session scan A b09e75651b31

Subscribe to this mod's changes

PlanVisualizer AGENTS.md is an instructions file published in the GitHub repository ksyed0/PlanVisualizer (6 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 8,993 tokens to every session, about $0.0360 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-31.

Planning

PlanVisualizer AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
PlanVisualizer AGENTS.mdksyed0/PlanVisualizer	Instructions file	6	3mo ago	Apache-2.0	A	8,993	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

PlanVisualizer: Instructions file for Codex