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/devolutions/avalonia-extensions/agents-mdgit clone --depth 1 https://github.com/Devolutions/avalonia-extensionsWhat 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.00637 | $0.00637 |
| Opus 5 | $0.00318 | $0.00318 |
| Sonnet 5 | $0.00127 | $0.00127 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
avalonia-extensions 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 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Assistant Guidelines
⚠️ REQUIRED: Session Pre-flight Check
Before starting any task, run this check:
ls .claude/local/
If the output contains only README.md (no other files), or if .vscode/ is missing, you must run the worktree setup script before doing anything else:
bash scripts/setup-worktree.sh
On Windows: pwsh scripts/setup-worktree.ps1
This copies gitignored local config (personal commands, .vscode/ settings) from the main worktree. Skipping it means you'll be missing developer-specific tooling and commands for this session.
Note: This file has been superseded by more comprehensive documentation in the
.claude/directory.
For detailed instructions on working with this repository as an AI assistant, please see:
.claude/CLAUDE.md - Main documentation covering:
- Repository overview and structure
- Development commands and workflows
- Architecture and design patterns
- Coding rules and best practices
- Version control guidelines
- Custom commands (
/worksetup,/commit,/explain,/simplify) - SampleApp + visual regression test workflow (see
README.mdTesting section)
Quick Reference
For human developers, see the main README.md for getting started.
Key AI assistant resources in .claude/:
CLAUDE.md- Primary instructions and project overviewcommands/- Custom slash commands for theme switching, commits, etc.commands/commit.md- Commit safety rules and/worksetupfile exclusionscommands/worksetup.md- Theme/tab/scale setup workflow forsamples/SampleApp/docs/- Process documentation and planning materialslocal/- Personal commands and docs (gitignored, developer-specific — check if it exists)
Key Development Workflows:
- Building/Running:
dotnet build samples/SampleApp/SampleApp.csproj && cd samples/SampleApp/bin/Debug/net10.0 && dotnet SampleApp.dll( Required for proper theme detection) - Notifications: Use non-blocking
osascript -e $'display dialog "..."' &(with ANSI-C quoting and&) for critical alerts. - Accelerate Controls: Requires
.envwithAVALONIA_LICENSE_KEY=your_key_hereat repository root. - Testing:
dotnet test(UseUPDATE_BASELINES=true dotnet teston macOS/Linux to update baseline screenshots if visual changes are intentional).
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 · 63 lines · 637 tokens per session scan A a6cdf1213880
avalonia-extensions AGENTS.md is an instructions file published in the GitHub repository Devolutions/avalonia-extensions (79 stars, last pushed 4d ago), licensed MIT. It adds 637 tokens to every session, about $0.0032 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.
buildNext
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).
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.
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).
spec-kit 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.
langchain 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.