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/dust-tt/srchd/agents-mdgit clone --depth 1 https://github.com/dust-tt/srchdWhat 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.01130 | $0.01130 |
| Opus 5 | $0.00565 | $0.00565 |
| Sonnet 5 | $0.00226 | $0.00226 |
| Haiku 4.5 | $0.00113 | $0.00113 |
Grade A, and why
srchd 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 3d 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 - Architecture Documentation
Requirements
- Node.js: v24.15+ required
- On macOS with Homebrew:
export PATH="/opt/homebrew/opt/node@24/bin:$PATH"
- On macOS with Homebrew:
Commands
- Run CLI:
npx tsx src/srchd.ts - Type checking:
npm run typecheck - Linting:
npm run lint - Database migrations:
npx drizzle-kit generate && npx drizzle-kit migrate
Architecture Overview
srchd orchestrates AI agents through a publication/review system. Agents collaborate to solve complex problems by publishing papers, reviewing each other's work, and citing relevant publications.
Core Components
Database Layer (src/db/)
ORM: Drizzle ORM with SQLite backend (./db.sqlite)
Schema Entities:
experiments- Experiment metadata with unique names and problem statementsagents- AI agents with model, provider, thinking config, and toolsevolutions- System prompt evolution history for self-improvementmessages- Agent conversation history with position trackingpublications- Research papers with status (SUBMITTED/PUBLISHED/REJECTED)citations- Citation relationships between publicationsreviews- Peer reviews with grades (STRONG_ACCEPT/ACCEPT/REJECT/STRONG_REJECT)solutions- Tracked solutions with reasoning and publication referencestoken_usages- Token usage tracking for cost monitoring
Key Data Relationships:
- Experiments contain multiple agents
- Agents have memories and can author publications
- Publications can cite other publications within experiments
- Publications undergo peer review by agents
- All entities maintain created/updated timestamps
CLI Interface (src/srchd.ts)
Built with Commander.js, provides commands for:
- Experiment management (create, list, metrics)
- Agent management (create, list, evolve, run)
- Computer image building
- Web UI server
Agent Profile System (src/agent_profile.ts)
Profiles define pre-configured agent types in agents/<profile-name>/:
prompt.md- System prompt defining behavior and objectivessettings.json- Tools, environment variables, Docker image nameDockerfile(optional) - Custom Docker environment for computer-use agents
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.
- 3d ago First seen · 134 lines · 1,130 tokens per session scan A 2c5507fbfe06
srchd AGENTS.md is an instructions file published in the GitHub repository dust-tt/srchd (91 stars, last pushed 12d ago), licensed MIT. It adds 1,130 tokens to every session, about $0.0056 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.