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/baalimago/slivingdoc/agents-mdgit clone --depth 1 https://github.com/baalimago/slivingdocWrote 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/baalimago/slivingdoc/agents-md)<a href="https://agentmods.dev/instructions/baalimago/slivingdoc/agents-md"><img src="https://agentmods.dev/badge/instructions/baalimago/slivingdoc/agents-md.svg" alt="Measured on agentmods" 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 | $0.05769 | $0.05769 |
| Opus 5 | $0.02884 | $0.02884 |
| Sonnet 5 | $0.01154 | $0.01154 |
| Haiku 4.5 | $0.00577 | $0.00577 |
Grade A, and why
slivingdoc AGENTS.md scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
raw, usage, err := p.fetch(ctx, req) How it starts
The opening of the file, as written. The whole thing — 490 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — slivingdoc
Architecture
slivingdoc is a standalone MCP server that gives many agents one shared
directory of UTF-8 text notes, stored durably in S3-compatible object storage.
It uses Git data structures and merge behavior internally but never invokes a
Git executable and never exposes a Git repository. The full contract is
docs/slivingdoc-v1.md. Three states
shape every operation. L is the caller-controlled visible directory.
P is the server-owned private state (repository, baseline, locks).
R is the accepted remote state indexed by the S3 object current.
MCP client (agent) human shell
notes_pull / notes_commit pull [path] / commit [path] -m <msg>
| |
| stdio JSON-RPC / one-shot argv
v v
+----------------------------------------------+
| main.go -> internal/cli |
| command router: serve | pull | commit | |
| version |
+----------------------+-----------------------+
|
v
+----------------------------------------------+
| cmd/serve -> internal/app |
| process body, engine lifecycle, version |
+----------------------+-----------------------+
|
v
+----------------------------------------------+
| internal/notebook.Notebook |
| Pull . Commit . recovery . checkpoint . |
| cleanup -- orchestration policy |
+----------+----------------------------+------+
| |
| workspace ops | storage protocol
v v
+--------------------------+ +----------------------------+
| internal/workspace | | internal/storage |
| L: visible path | | manifest v1, pack keys, |
| P: private dir | | ETag CAS, probe |
| os.Root scan, state.json| +-------------+--------------+
| op lock (sem + flock) | |
+------------+-------------+ |
| ObjectStore adapter |
| v
| +----------------------------+
| | internal/s3store (AWS SDK)|
| | --> S3-compatible bucket |
| +----------------------------+
v
+--------------------------+
| internal/git |
| Go seam + policy: |
| trees, snapshots, merge,|
| packs, shallow history |
+------------+-------------+
|
v
+--------------------------+
| internal/git2 (CGo) |
| libgit2 v1.9.6 static; |
| never git2go, never a |
| Git binary |
+--------------------------+
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 · 490 lines · 5,769 tokens per session scan A 52c7a66445fc
slivingdoc AGENTS.md is an instructions file published in the GitHub repository baalimago/slivingdoc (1 stars, last pushed 4d ago), licensed MIT. It adds 5,769 tokens to every session, about $0.0288 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
chunkhound AGENTS.md
AGENTS.md instructions for chunkhound/chunkhound, covering chunkhound llm context, projectidentity, modificationrules, keycommands and development.
mcp AGENTS.md
AGENTS.md instructions for Teamwork/mcp, covering agents.md, this repository is public, project overview, setup commands and build and run.
raindrop-mcp GEMINI.md
Instructions for adeze/raindrop-mcp, covering raindrop mcp server - project context, project overview, core technologies, architecture and key commands.
raindrop-mcp copilot-instructions.md
Instructions for adeze/raindrop-mcp: The canonical project instructions are in AGENTS.md. Follow them for architecture, MCP safety constraints, tooling, validation, and release policy.
raindrop-mcp CLAUDE.md
Instructions for adeze/raindrop-mcp: Project instructions moved to AGENTS.md, the canonical Codex operating guide.
obsidian-vault-mcp CLAUDE.md
Claude Code instructions for ebullient/obsidian-vault-mcp, covering obsidian vault mcp, code style and qa.