Borrowing it
Nothing to install: this file belongs to LunarWerxs/RepoYeti. 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/LunarWerxs/RepoYeti/main/AGENTS.mdgit clone --depth 1 https://github.com/LunarWerxs/RepoYetiWrote 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/lunarwerxs/repoyeti/agents-md)<a href="https://agentmods.dev/instructions/lunarwerxs/repoyeti/agents-md"><img src="https://agentmods.dev/badge/instructions/lunarwerxs/repoyeti/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.01921 | $0.01921 |
| Opus 5 | $0.00960 | $0.00960 |
| Sonnet 5 | $0.00384 | $0.00384 |
| Haiku 4.5 | $0.00192 | $0.00192 |
Grade A, and why
RepoYeti 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Orientation for an AI agent (or a new human) about to change this repository. It is a map and a list of traps, not a tutorial. The deep documents are docs/ARCHITECTURE.md (what this is and why it is shaped this way) and docs/CONTRIBUTING.md (setup, i18n, test conventions, the git-safety rules). Read this first, then the one you need.
RepoYeti is openly AI-built, and issues are the working surface. If you are an agent reading this because someone pointed you at a bug report, the report is usually the best spec in the room.
The one thesis
A background daemon on the machine that owns the repositories, and a dashboard you reach from a phone. Nothing is uploaded, nothing is mirrored, no server holds the code. Every design decision follows from that; if a change would require code to leave the machine, it is the wrong change.
Layout
| Path | What lives there |
|---|---|
src/ |
The daemon: git orchestration, HTTP API, auth, discovery, auto-update, CLI. Bun + TypeScript. |
web/ |
The dashboard. Its own package with its own package.json, deps, and test runner. Vue 3 + reka-ui + Tailwind. |
tests/ |
Daemon tests (bun test). |
web/test/ |
Dashboard tests (Vitest + jsdom). |
scripts/ |
Build, release, and the guardrail checks. scripts/checks/ holds the standalone ones. |
relay/ |
The Cloudflare Worker behind the permanent app.repoyeti.com/r/<id> address. Deployed separately. |
site/ |
The static marketing site. Not part of the app. |
misc/ |
Windows tray launch chain. Partly kit-managed, see below. |
docs/ |
Architecture, contributing, the stable-address guide, the Buzz protocol. |
Before you push
There are two package roots and two test runners. Running only one of them is the single most common way to push something broken here.
# daemon
bun test
bun run typecheck
bun run check # lint + every guardrail below
bun run check:coverage # coverage floor
# dashboard
bun run --cwd web test # Vitest
bun run --cwd web build # runs i18n:check, then vue-tsc, then the bundle
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 · 134 lines · 1,921 tokens per session scan A 7f76b8a184eb
RepoYeti AGENTS.md is an instructions file published in the GitHub repository LunarWerxs/RepoYeti (28 stars, last pushed yesterday), licensed MIT. It adds 1,921 tokens to every session, about $0.0096 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).
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).
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.