AIRI is a self-hosted virtual AI companion that gives an AI character a voice, visual presence, memory, and the ability to interact with games and coding activity. People use it as a personal digital companion on the web, macOS, or Windows, including for voice chat and gameplay. The catalogue add-ons provide workflows for working with the AIRI project.
Borrowing it
Nothing to install: this file belongs to moeru-ai/airi. 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/moeru-ai/airi/main/AGENTS.mdgit clone --depth 1 https://github.com/moeru-ai/airiWrote 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/moeru-ai/airi/agents-md)<a href="https://agentmods.dev/instructions/moeru-ai/airi/agents-md"><img src="https://agentmods.dev/badge/instructions/moeru-ai/airi/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.06841 | $0.06841 |
| Opus 5 | $0.03420 | $0.03420 |
| Sonnet 5 | $0.01368 | $0.01368 |
| Haiku 4.5 | $0.00684 | $0.00684 |
Grade A, and why
airi 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 — 346 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project AIRI Agent Guide
Concise but detailed reference for contributors working across the moeru-ai/airi monorepo. Improve code when you touch it; avoid one-off patterns.
Tech Stack (by surface)
- Desktop (stage-tamagotchi): Electron, Vue, Vite, TypeScript, Pinia, VueUse, Eventa (IPC/RPC), UnoCSS, Vitest, ESLint.
- Web (stage-web): Vue 3 + Vue Router, Vite, TypeScript, Pinia, VueUse, UnoCSS, Vitest, ESLint. Backend: WIP.
- Mobile (stage-pocket): Vue 3 + Vue Router, Vite, TypeScript, Pinia, VueUse, UnoCSS, Vitest, ESLint, Kotlin, Swift, Capacitor.
- UI/Shared Packages:
packages/stage-ui: Core business components, composables, stores shared by stage-web & stage-tamagotchi (heart of stage work).packages/stage-ui-three: Three.js bindings + Vue components.packages/stage-ui-pixi: Planned Pixi bindings.packages/stage-shared: Shared logic across stage-ui, stage-ui-three, stage-web, stage-tamagotchi.packages/ui: Standardized primitives (inputs, textarea, buttons, layout) built on reka-ui; minimal business logic.packages/i18n: Central translations.- Server channel:
packages/server-runtime,packages/server-sdk,packages/server-shared(powerservices/andplugins/). - Legacy:
crates/(old Tauri desktop; current desktop is Electron).
Structure & Responsibilities
- Hosted backend (
server/)server/apps/api: Hono resource API and business domains.server/apps/auth: standalone Better Auth and OIDC service.server/packages: backend-private schema and Node infrastructure packages.server/dev/caddy: local-only Auth/API edge routing.server/docker-compose.yaml: complete local backend stack.
- Apps
apps/stage-web: Web app; composables/stores insrc/composables,src/stores; pages insrc/pages; devtools insrc/pages/devtools; router config viavite.config.ts.apps/stage-tamagotchi: Electron app; renderer pages insrc/renderer/pages; devtools insrc/renderer/pages/devtools; settings layout atsrc/renderer/layouts/settings.vue; router config viaelectron.vite.config.ts.- Settings/devtools routes rely on
<route lang="yaml"> meta: layout: settings </route>; ensure routes/icons are registered accordingly (apps/stage-tamagotchi/src/renderer/layouts/settings.vue,apps/stage-web/src/layouts/settings.vue). - Shared page bases:
packages/stage-pages. - Stage pages:
apps/stage-web/src/pages,apps/stage-tamagotchi/src/renderer/pages(plus devtools folders).
- Stage UI internals (
packages/stage-ui/src)- Providers:
stores/providers.tsandstores/providers/(standardized provider definitions). - Modules:
stores/modules/(AIRI orchestration building blocks). - Composables:
composables/(business-oriented Vue helpers). - Components:
components/; scenarios incomponents/scenarios/for page/use-case-specific pieces. - Stories:
packages/stage-ui/stories,packages/stage-ui/histoire.config.ts(e.g.components/misc/Button.story.vue).
- Providers:
- IPC/Eventa: Always use
@moeru/eventafor type-safe, framework/runtime-agnostic IPC/RPC. Define contracts centrally (e.g.,apps/stage-tamagotchi/src/shared) and follow usage patterns inapps/stage-tamagotchi/src/main/services/electronfor main/renderer integration. - Dependency Injection: Use
injecafor services/electron modules/plugins/frontend; seeapps/stage-tamagotchi/src/main/index.tsfor composition patterns. - Build/CI/Lint:
.github/workflowsfor pipelines;eslint.config.jsfor lint rules. - Styles: UnoCSS config at
uno.config.ts; checkapps/stage-web/src/stylesfor existing animations; prefer UnoCSS over Tailwind.
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 · 346 lines · 6,841 tokens per session scan A 490883e87803
airi AGENTS.md is an instructions file published in the GitHub repository moeru-ai/airi (48,813 stars, last pushed today), licensed MIT. It adds 6,841 tokens to every session, about $0.0342 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
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.
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).
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.