Borrowing it
Nothing to install: this file belongs to OtterMind/youclaw. 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/OtterMind/youclaw/main/AGENTS.mdgit clone --depth 1 https://github.com/OtterMind/youclawWrote 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/ottermind/youclaw/agents-md)<a href="https://agentmods.dev/instructions/ottermind/youclaw/agents-md"><img src="https://agentmods.dev/badge/instructions/ottermind/youclaw/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/ottermind/youclaw/agents-md"><img src="https://agentmods.dev/badge/instructions/ottermind/youclaw/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00783 | $0.00783 |
| Opus 5.5 | $0.00313 | $0.00313 |
| Sonnet 5.5 | $0.00157 | $0.00157 |
| Haiku 4.5 | $0.00078 | $0.00078 |
Grade A, and why
youclaw 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 1mo 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 — 28 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
The Bun backend lives in src/, organized by domain: agent/, channel/, db/, routes/, scheduler/, memory/, and skills/. End-to-end and database-heavy tests live in tests/, with occasional colocated tests such as src/agent/manager.test.ts. The React/Vite frontend lives in web/src/; static assets are in web/public/ and web/src/assets/. Runtime data is stored under data/, while agent definitions live in agents/<agent-id>/.
Build, Test, and Development Commands
Use Bun for both workspaces.
bun run dev: start the backend with hot reload on portPORT(default62601).bun run start: run the backend without hot reload.bun run dev:web: start the frontend dev server fromweb/.bun test: run the Bun test suite.bun run typecheck: run root TypeScript checks.cd web && bun run lint: lint the frontend with ESLint.cd web && bun run build: type-check and build the frontend bundle.
Coding Style & Naming Conventions
Write TypeScript with 2-space indentation, single quotes, and no semicolons; match nearby files when in doubt. Keep backend modules small and domain-focused. Use PascalCase for React components/pages (Tasks.tsx), camelCase for functions/hooks (useChat.ts), and descriptive directory names (src/routes, web/src/components/ui). Frontend lint rules are defined in web/eslint.config.js; no Prettier config is checked in, so avoid formatting-only churn.
Testing Guidelines
Tests use bun:test. Name files *.test.ts and prefer colocated tests for tight unit coverage or tests/ for integration scenarios. Reuse tests/setup.ts for shared env and SQLite setup. No coverage threshold is enforced today; add regression tests for any route, scheduler, DB, or i18n behavior you change.
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.
- 1mo ago First seen · 28 lines · 783 tokens per session scan A 430074d6f251
youclaw AGENTS.md is an instructions file published in the GitHub repository OtterMind/youclaw (724 stars, last pushed 6mo ago), licensed MIT. It adds 783 tokens to every session, about $0.0031 per session on Opus 5.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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.