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 agentmods add instructions/ksyed0/planvisualizer/claude-mdgit clone --depth 1 https://github.com/ksyed0/PlanVisualizerWrote 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/ksyed0/planvisualizer/claude-md)<a href="https://agentmods.dev/instructions/ksyed0/planvisualizer/claude-md"><img src="https://agentmods.dev/badge/instructions/ksyed0/planvisualizer/claude-md.svg" alt="Measured on agentmods" 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 | $0.00884 | $0.00884 |
| Opus 5 | $0.00442 | $0.00442 |
| Sonnet 5 | $0.00177 | $0.00177 |
| Haiku 4.5 | $0.00088 | $0.00088 |
Grade A, and why
PlanVisualizer CLAUDE.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 3d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — Claude Code Session Instructions
Platform file for Claude Code. The authoritative operating standards are in
AGENTS.md. This file adds Claude-specific directives and serves as the session entry point.
Mandatory Session Startup
- Read
AGENTS.mdin full before writing any code or using any tools. - Read
MEMORY.mdand all linked topic files. - Read
PROMPT_LOG.mdto understand the prompt history and where the last session ended. - Check
docs/ID_REGISTRY.mdbefore creating any new artefact (epic, story, task, AC, TC, bug).
Project at a Glance
- Repo:
ksyed0/PlanVisualizer - Purpose: Parse project markdown files and generate a static HTML dashboard.
- Entry point:
node tools/generate-plan.js - Dashboard:
https://ksyed0.github.io/PlanVisualizer/plan-status.html - Project Constitution:
PROJECT.md(create if missing; see AGENTS.md §3)
Key Protocols (from AGENTS.md)
| Protocol | Rule |
|---|---|
| §1 Sequential Execution | Disabled — parallel agents permitted |
| §4 Prompt Logging | Log every user prompt to PROMPT_LOG.md with timestamp |
| §8 Unit Testing | ≥80% coverage; all tests pass before any commit |
| §11 Git Workflow | feature/* → develop (PR) → main (PR). Never push directly to main or develop |
| §14 Session Close | Update progress.md, MEMORY.md, PROMPT_LOG.md, LESSONS.md, MIGRATION_LOG.md before ending |
Git Branching Quick Reference
feature/US-XXXX-short-name → squash-merge into develop via PR
bugfix/BUG-XXXX-short-name → squash-merge into develop via PR
release/X.Y.Z → merge into main via PR
hotfix/BUG-XXXX-short-name → branch from main, merge into main + develop
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.
- 3d ago First seen · 73 lines · 884 tokens per session scan A a6374f38d047
PlanVisualizer CLAUDE.md is an instructions file published in the GitHub repository ksyed0/PlanVisualizer (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 884 tokens to every session, about $0.0044 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-31.
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).
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.
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.
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 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).
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.