Borrowing it
Nothing to install: this file belongs to solo-agent/solo. 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/solo-agent/solo/master/AGENTS.mdgit clone --depth 1 https://github.com/solo-agent/soloWrote 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/solo-agent/solo/agents-md)<a href="https://agentmods.dev/instructions/solo-agent/solo/agents-md"><img src="https://agentmods.dev/badge/instructions/solo-agent/solo/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/solo-agent/solo/agents-md"><img src="https://agentmods.dev/badge/instructions/solo-agent/solo/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.00306 | $0.00306 |
| Opus 5.5 | $0.00122 | $0.00122 |
| Sonnet 5.5 | $0.00061 | $0.00061 |
| Haiku 4.5 | $0.00031 | $0.00031 |
Grade A, and why
solo 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.
What it actually says
Project testing rules
- Before implementation, produce a complete architecture design covering the domain model, ownership and lifecycle, data flow, persistence, APIs, frontend state, failure recovery, migration, and compatibility with existing Solo behavior.
- Review every change from the whole-project perspective. Trace the existing frontend, server, daemon, local agent runtime, session, and database paths before changing one feature path.
- All new product-flow validation must use real components and dependencies; do not use mocks.
- End-to-end tests must use the real frontend, API server, and PostgreSQL database.
- Do not mock HTTP routes, backend services, or database behavior.
- Validation must cover frontend behavior and the complete backend path, including the real local agent runtime when the feature invokes agents; UI-only tests are not sufficient.
- Report E2E success only after verifying the user-visible result and persisted database state.
Project service lifecycle rules
- An agent may start or restart the Solo frontend, API server, and daemon when requested, but only by running
make rebuildfrom the repository root. Tests must reuse that make-managed stack. - Never create
launchctljobs or manually start these services with direct binaries,go run,npm run dev,nohup, or custom background commands. - When the user asks to stop the project, use
make stopand verify that ports 3000, 8080, and 8081 are no longer listening. Do not restart services unless the user explicitly asks.
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 · 16 lines · 306 tokens per session scan A 0adca1eec102
solo AGENTS.md is an instructions file published in the GitHub repository solo-agent/solo (595 stars, last pushed 1mo ago), licensed MIT. It adds 306 tokens to every session, about $0.0012 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.