Borrowing it
Nothing to install: this file belongs to silo-code/silo. 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/silo-code/silo/main/AGENTS.mdgit clone --depth 1 https://github.com/silo-code/siloWrote 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/silo-code/silo/agents-md)<a href="https://agentmods.dev/instructions/silo-code/silo/agents-md"><img src="https://agentmods.dev/badge/instructions/silo-code/silo/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/silo-code/silo/agents-md"><img src="https://agentmods.dev/badge/instructions/silo-code/silo/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.04900 | $0.04900 |
| Opus 5.5 | $0.01960 | $0.01960 |
| Sonnet 5.5 | $0.00980 | $0.00980 |
| Haiku 4.5 | $0.00490 | $0.00490 |
Grade A, and why
silo 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 25d 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 — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Silo — project guide for coding agents
Silo keeps all your projects alive at once — for developers juggling coding agents (Tauri + React + TypeScript). Open many workspaces and switch instantly; each keeps its terminals, agents, panels, and layout intact in the background. 100% open source, free forever. Extensible: modeled on VS Code / Obsidian with a small stable core, a public extension SDK, and first-party features built as extensions — so the bar for boundaries, documentation, and a clean public surface is high.
Product positioning for humans lives in README.md / apps/docs/index.md /
context7.json. Prefer those over inventing a tagline. This file is agent
orientation (architecture, boundaries, commands), not marketing copy.
Orientation docs (read when relevant):
docs/architecture.md— the structural map: packages and their dependency edges, layering inside the host, the Rust/webview process split, persistence destinations, and the two published surfaces. Facts-only and drift-checked; start here when you don't yet know where something lives. The rules for staying inside those boundaries are below, under "Architecture boundaries".docs/architecture-review-workflow.md— how a change gets an architectural review end to end: thesilo-architecture-reviewskill, spot-checking its findings, and the author → reviewer → fixer session split.docs/decisions/— ADRs: the architecture decisions of record (the durable "why").docs/proposals/— RFCs: forward-looking designs not yet decided.docs/change-planning-convention.md— how a substantial change is planned: proposal → (temporary) planning package → implementation → verification → collapse back to one durable proposal. See "Planning a substantial change" below.docs/domain-language.md— the domain glossary: ubiquitous language for the product, including UI component naming (Panels & Docking, Navigator, …). Kept current via the workflow in.agents/skills/silo-domain-modeling/SKILL.md.docs/silo-extensions-repo.md— the externalsilo-code/silo-extensionsrepo (cloned at../silo-extensions): how its third-party extensions relate to this repo — published-SDK lag, npm (not pnpm) build commands, runtime trust /silo.permissions, and how to install a branch without merging. They publish into the registry; discovery is Browse / extensions.getsilo.dev, not cloning that repo.docs/extensions-registry-repo.md— the externalsilo-code/extensions-registryrepo (cloned at../extensions-registry): git-backed catalog behind extensions.getsilo.dev (humans) and registry.getsilo.dev (app/CLI index). How it relates to in-app Browse / install / update in this monorepo.apps/docs/guide/extension-checklist.md— pre-flight checklist for any extension (bundled or third-party): boundaries, permissions, styling, lifecycle, packaging, stability.
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.
- 25d ago Changed · +9 lines · +114 tokens per session 11d41c14c94f
- 1mo ago Changed · +38 lines · +532 tokens per session ae4b03ccbbd4
- 1mo ago Changed · +3 lines · +50 tokens per session 982bbdfbefdd
- 1mo ago First seen · 295 lines · 4,204 tokens per session scan A 1f57f44d2b18
silo AGENTS.md is an instructions file published in the GitHub repository silo-code/silo (62 stars, last pushed yesterday), licensed MIT. It adds 4,900 tokens to every session, about $0.0196 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).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.