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 agents/silo-code/silo/indexgit 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.00000 | $0.00569 |
| Opus 5 | $0.00000 | $0.00284 |
| Sonnet 5 | $0.00000 | $0.00114 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
index 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ctx.agents
Host-computed coding-agent activity and resume-identity observability — a
live, read-only view of what each terminal's agent is doing, plus an honest
resume hint when a session's backend dies uncleanly. The companion to
ctx.processes (foreground process facts); this surface
is for agent activity and resume identity. Detection is sealed in the host
— there is no registerAgent / detector API.
ctx.agents: AgentsService
Example
Notify when a session dies with a resume command
export const extension: Extension = {
id: "my.agent-resume-toast",
activate(ctx) {
const sub = ctx.agents.subscribe((agents) => {
const dead = agents.find((a) => a.activity === "dead" && a.resumeCommand);
if (dead) ctx.ui.notify("info", dead.resumeCommand!);
});
ctx.subscriptions.push(sub);
},
};
Acknowledge finished runs when the user looks at the terminal
needsAttention is separate from activity === "idle". The host never
auto-clears attention on focus — that is a per-consumer policy:
ctx.subscriptions.push(
ctx.terminals.subscribeActive((terminalId) => {
if (terminalId) ctx.agents.acknowledge(terminalId);
}),
);
What you get
| Field | Meaning |
|---|---|
activity |
none | working | idle | error | dead |
needsAttention |
Sticky "finished while you weren't looking" — cleared only by acknowledge |
sessionId / resumeCommand |
Exact resume when a Settings → Agents hook (or native session file) resolved an id; otherwise an honest session-id-less note. Silo never infers an id from cwd/recency. |
agentId / agentName |
Catalog key + display name once a known agent leader is detected |
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 · 61 lines · 0 tokens per session scan A cd7922223603
index is an agent published in the GitHub repository silo-code/silo (53 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 569 tokens. 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 agents, from other repositories
project-structure-validator
Validates project structure against co-location and architecture patterns defined in AGENTS.md.
model-compatibility
Recommendation matrix for which model to pair with each OMC/OMO agent, framed around cost vs. quality. This page exists so the recurring "어떤 모델을 어느 agent에 박아야 함?" question stops being tribal Discord knowledge.
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
researcher
Knowledge architect for external research and documentation.
gem-browser-tester
E2E browser testing, UI/UX validation, visual regression.
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.