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/silo-code/silo/agents-mdgit clone --depth 1 https://github.com/silo-code/siloWhat 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.04204 | $0.04204 |
| Opus 5 | $0.02102 | $0.02102 |
| Sonnet 5 | $0.00841 | $0.00841 |
| Haiku 4.5 | $0.00420 | $0.00420 |
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 yesterday.
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 — 295 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/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.
- yesterday 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 (53 stars, last pushed yesterday), licensed MIT. It adds 4,204 tokens to every session, about $0.0210 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
agtx AGENTS.md
Instructions for fynnfluegge/agtx, covering agents.md, what is agtx?, build & test, key architecture and core concepts.
agtx CLAUDE.md
Instructions for fynnfluegge/agtx, covering agtx - terminal kanban for coding agents, quick start, build, run in a git project directory and or run in dashboard mode (no git project required).
cmux CLAUDE.md
Claude Code instructions for manaflow-ai/cmux, covering cmux agent notes, setup, build and reload, shared mac fleet capacity and tag-bound debug cli.
opencode-bar AGENTS.md
Instructions for opgginc/opencode-bar, covering important restriction, coding rules, branding guides, ui styling rules and explicit 'used' or 'left'.
superset AGENTS.md
AGENTS.md instructions for superset-sh/superset, covering superset monorepo, project structure, exception: shadcn/ui components, database and releases.
cmux AGENTS.md
AGENTS.md instructions for manaflow-ai/cmux, a project described as: Open source Ghostty-based macOS terminal with vertical tabs and notifications for AI coding agents. Built for multitasking, organization, and programmability.