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/marcinbunsch/overseer/agents-mdgit clone --depth 1 https://github.com/marcinbunsch/overseerWrote 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/marcinbunsch/overseer/agents-md)<a href="https://agentmods.dev/instructions/marcinbunsch/overseer/agents-md"><img src="https://agentmods.dev/badge/instructions/marcinbunsch/overseer/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 | $0.00567 | $0.00567 |
| Opus 5 | $0.00283 | $0.00283 |
| Sonnet 5 | $0.00113 | $0.00113 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
overseer 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 4d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Instructions for AI agents working on this codebase.
Project Context
Overseer is a desktop GUI frontend for AI coding agents (Claude Code, Codex, OpenCode). See docs/OVERSEER.md for full architecture, component map, data models, and feature documentation.
Key References
- docs/OVERSEER.md — Architecture, source structure, component map, data models, implemented features, planned features
- CLAUDE.md — Development commands, pre-commit checklist, tech stack, key conventions
- docs/claude-agent-sdk.md — Claude Agent SDK reference (query API, tools, hooks, subagents, MCP, permissions, sessions)
- docs/features/ — Implemented feature specs
- docs/plans/ — Planned feature specs
Design Principles
- Private: No telemetry, no API keys, no cloud integrations. Never add analytics, tracking, or external service calls.
- Performant: No idle polling, no background refreshes. Everything is event-driven and reactive. Minimize resource usage.
- Extensible: The
AgentServiceinterface allows new agent backends without modifying existing code. Keep this boundary clean.
Development
- Package manager: pnpm
- Run
pnpm checksbefore committing (orpnpm checks:uifor UI-only changes) - Run
pnpm testto verify changes - Frontend: React 19 + TypeScript 5.9 + MobX + Tailwind CSS v4
- Backend: Tauri v2 (Rust) in
src-tauri/
MobX Conventions
- NEVER use
makeAutoObservableormakeObservable— always use@observable,@computed, and@actiondecorators - Decorators go on a separate line above the member they decorate:
@observable pending: PendingNote | null = null @action updateComment(text: string) { // ... }
Finding Current Models
When updating model lists in src/renderer/stores/ConfigStore.ts, check these sources for the latest available models:
- Claude: Claude models overview
- Codex: OpenAI Models or Codex Models
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.
- 4d ago First seen · 51 lines · 567 tokens per session scan A 2201f2ddac2c
overseer AGENTS.md is an instructions file published in the GitHub repository marcinbunsch/overseer (11 stars, last pushed yesterday), licensed MIT. It adds 567 tokens to every session, about $0.0028 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
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.
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.
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).
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.