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/agavra/yuzudraw/agents-mdgit clone --depth 1 https://github.com/agavra/yuzudrawWrote 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/agavra/yuzudraw/agents-md)<a href="https://agentmods.dev/instructions/agavra/yuzudraw/agents-md"><img src="https://agentmods.dev/badge/instructions/agavra/yuzudraw/agents-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.1 | $0.02272 | $0.02272 |
| Opus 5 | $0.01136 | $0.01136 |
| Sonnet 5 | $0.00454 | $0.00454 |
| Haiku 4.5 | $0.00227 | $0.00227 |
Grade A, and why
yuzudraw 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 5d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YuzuDraw
A macOS app for drawing ASCII diagrams (Monodraw/Figma-like).
Build & Test
# Generate Xcode project (after modifying project.yml)
xcodegen generate
# Build (warnings are treated as errors via project.yml settings)
xcodebuild -scheme YuzuDraw -destination 'platform=macOS' build
# Run tests (UI smoke tests are excluded from the scheme; only unit tests run)
xcodebuild -scheme YuzuDraw -destination 'platform=macOS' test
# Build CLI
xcodebuild -project YuzuDraw.xcodeproj -scheme YuzuDrawCLI -configuration Debug build
Project Structure
project.yml— XcodeGen spec (source of truth for the Xcode project)YuzuDraw/App/— App entry point (YuzuDrawAppwithWorkspaceViewModel)YuzuDraw/Models/— Data models (Canvas, Geometry, Shapes, Layers, Document, ProjectMetadata, ProjectTab, RecentProject)YuzuDraw/Views/— SwiftUI views (RootView, WelcomeView, TabBarContentView, ContentView, CanvasView, ToolbarView, LayerPanel, InspectorPanel)YuzuDraw/ViewModels/— Observable view models (WorkspaceViewModel, EditorViewModel)YuzuDraw/Tools/— Drawing tool system (Tool protocol, SelectionTool, RectangleTool, ArrowTool, TextTool)YuzuDraw/Serialization/— Document persistence (JSON via DocumentCodable, DSL via DSLSerializer/DSLParser, ProjectFileManager for file I/O)YuzuDraw/Automation/— Shared automation service for CLI workflows (DiagramAutomationService)YuzuDrawCLI/— CLI entrypoint and command handlingYuzuDraw/Resources/— Assets, Info.plist, entitlementsYuzuDrawTests/— Unit tests
Architecture
Rendering Pipeline
Document (shapes, layers, groups) ← semantic model, source of truth
│
▼
RenderEngine: iterate layers bottom→top, render visible shapes
│
▼
Canvas (2D character grid) ← "framebuffer", re-rendered on every mutation
│
▼
CanvasView: displays Canvas.render() as monospaced Text
Canvasis a dumb 2D character grid — shapes are the source of truth, not canvas cellsDocument.render(into:)clears canvas then renders all visible layers/shapes in orderEditorViewModel.rerender()is called after every document mutation
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.
- 5d ago First seen · 159 lines · 2,272 tokens per session scan A 8c03239bfa8f
yuzudraw AGENTS.md is an instructions file published in the GitHub repository agavra/yuzudraw (50 stars, last pushed 5mo ago), licensed MIT. It adds 2,272 tokens to every session, about $0.0114 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
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.
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.
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.
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).