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/wolfenazz/yzpzcode/claude-mdgit clone --depth 1 https://github.com/wolfenazz/YzPzCodeWhat 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.04878 | $0.04878 |
| Opus 5 | $0.02439 | $0.02439 |
| Sonnet 5 | $0.00976 | $0.00976 |
| Haiku 4.5 | $0.00488 | $0.00488 |
Grade A, and why
YzPzCode 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 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.
How it starts
The opening of the file, as written. The whole thing — 394 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
YzPzCode is a Tauri v2 desktop application that provides a unified interface for multiple AI coding CLI tools and SaaS tool CLIs. It combines a React 19 frontend with a Rust backend to create a native, cross-platform development environment with an in-app browser, visual design inspector, AI-powered designer, and multi-workspace management.
Tech Stack:
- Frontend: React 19 + TypeScript, Vite 6, Tailwind CSS v4, Zustand 5, CodeMirror 6, xterm.js 6, framer-motion, @iconify/react
- Backend: Tauri v2, Rust, portable-pty, Tokio, discord-rich-presence
- Development: Node.js 18+, Rust (latest stable)
Development Commands
# Navigate to app directory first
cd app
# Development
npm install # Install dependencies
npm run tauri dev # Run development server (opens on port 8745)
# Building
npm run build # Build frontend only
npm run tauri build # Build production installers
# Type Checking
npx tsc --noEmit # Frontend type checking
cd src-tauri && cargo check # Backend type checking
# Rust-specific
cd src-tauri
cargo test # Run tests
cargo clippy # Lint
cargo fmt # Format code
Architecture
Frontend-Backend Communication
The app uses Tauri's IPC (Inter-Process Communication) for all frontend-backend communication:
- Frontend calls Tauri commands via
@tauri-apps/api/core - Backend defines commands in
src-tauri/src/commands/with#[tauri::command] - Real-time events:
app.emit("event-name", payload)from Rust,listen<T>("event-name", callback)from frontend - No direct REST APIs - all communication through Tauri IPC
State Management
- Zustand (
app/src/stores/appStore.ts): Centralized state withpersistmiddleware - Updater Store (
app/src/stores/updaterStore.ts): Auto-update state (checking, downloading, progress) - Key state slices include:
- Workspace management (currentWorkspace, workspaceList, openWorkspaces, multi-workspace tabs)
- Terminal sessions (sessions, activeSessionId, per-workspace session tracking)
- CLI statuses (cliStatuses, toolCliStatuses) — both AI agents and tool CLIs
- Authentication states (authInfos, toolAuthInfos)
- UI settings (theme, accent color, UI density, animations, custom cursor, terminal, editor)
- File editor (openFiles, activeFilePath, dirty state tracking, workspace file isolation)
- Browser state (URL, tabs, zoom, inspect/pickStyle/apply modes, style clipboard, UI references)
- IDE detection (ideStatuses, selectedIdes)
- Version updates (autoCheck, autoDownload, channel, updateAvailable)
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.
- 2d ago First seen · 394 lines · 4,878 tokens per session scan A bf8c7b6a2efd
YzPzCode CLAUDE.md is an instructions file published in the GitHub repository wolfenazz/YzPzCode (11 stars, last pushed 7d ago), licensed Apache-2.0. It adds 4,878 tokens to every session, about $0.0244 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 instructions, from other repositories
superset CLAUDE.md
Claude Code instructions for superset-sh/superset, a project described as: Superset is an agentic IDE to orchestrate 100+ coding agents in parallel. Run any agent with your own subscription.
ai-workflow AGENTS.md
Instructions for cunhaax/ai-workflow, covering ai workflow template, rules — non-negotiable, project overview, commands and architecture.
trackly-cli CLAUDE.md
Claude Code instructions for trackly-app/trackly-cli, covering trackly-cli, tech stack, backend production source of truth, directory structure and key commands.
com-example-config-AsyncTestConfig
Instructions for PIsberg/vibetags, covering copilot instructions for asynctestconfig and immutable type.
pupila CLAUDE.md
Instructions for FranRom/pupila, covering claude.md, where things live, stack, run locally and repo layout.
claude-bridge AGENTS.md
Instructions for kadaba/claude-bridge, covering agents.md — using claude-bridge from any ai coding cli, two independent channels, 1. coordination (the conversation), 2. file transfer (the bytes) — same for every tool and workflows.