Borrowing it
Nothing to install: this file belongs to XMihura/Kanvas. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/XMihura/Kanvas/main/AGENTS.mdgit clone --depth 1 https://github.com/XMihura/KanvasWrote 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/xmihura/kanvas/agents-md)<a href="https://agentmods.dev/instructions/xmihura/kanvas/agents-md"><img src="https://agentmods.dev/badge/instructions/xmihura/kanvas/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.01009 | $0.01009 |
| Opus 5 | $0.00504 | $0.00504 |
| Sonnet 5 | $0.00202 | $0.00202 |
| Haiku 4.5 | $0.00101 | $0.00101 |
Grade A, and why
Kanvas 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 7d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Canvas Workflow — Agent Instructions
This project uses Obsidian Canvas files as visual task boards. A Python CLI tool manages all board modifications.
CRITICAL RULE
NEVER edit .canvas files directly. All canvas modifications MUST go through the CLI tool:
python canvas-tool.py "<file>.canvas" <command> [args]
Direct JSON editing of .canvas files is forbidden. The CLI tool enforces workflow rules (valid transitions, cycle detection, blocked states) so you don't have to remember them.
Session Protocol
1. Start of session — read the board
python canvas-tool.py "Project.canvas" status
Review the board state. Run normalize if needed. Report ready tasks, blocked tasks, and any anomalies to the user.
2. Pick a task
python canvas-tool.py "Project.canvas" ready # see what's available
python canvas-tool.py "Project.canvas" show <TASK-ID> # read task details
python canvas-tool.py "Project.canvas" start <TASK-ID> # begin work (red → orange)
If multiple tasks are ready, ask the user which to prioritize.
3. Work on the task
Execute the task. If you discover subtasks, propose them:
python canvas-tool.py "Project.canvas" propose Development "Subtask title" "Description" --depends-on DV-01
Update notes on your in-progress task:
python canvas-tool.py "Project.canvas" edit <TASK-ID> "Updated description with findings."
4. Finish the task
python canvas-tool.py "Project.canvas" finish <TASK-ID> # orange → cyan
Tell the user what was done. Do NOT attempt to set the card green — only the human does that.
5. Repeat
After the human marks your task green, check for newly unblocked tasks:
python canvas-tool.py "Project.canvas" normalize
python canvas-tool.py "Project.canvas" ready
What you CAN do
- Read the board:
status,show,list,blocked,blocking,ready,dump - Normalize the board:
normalize - Propose tasks:
proposeorbatch(creates purple cards) - Propose groups:
propose-grouporbatch - Start a task:
start <ID>(red → orange) - Finish a task:
finish <ID>(orange → cyan) - Pause a task:
pause <ID>(orange → red) - Edit task text:
edit <ID> "<text>"(only orange tasks) - Add dependencies:
add-dep <FROM> <TO>
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.
- 7d ago First seen · 132 lines · 1,009 tokens per session scan A b0b5e0467296
Kanvas AGENTS.md is an instructions file published in the GitHub repository XMihura/Kanvas (194 stars, last pushed 5mo ago), licensed MIT. It adds 1,009 tokens to every session, about $0.0050 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).
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
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.
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.