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/dsebastien/obsidian-cli-rest/agents-mdgit clone --depth 1 https://github.com/dsebastien/obsidian-cli-restWrote 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/dsebastien/obsidian-cli-rest/agents-md)<a href="https://agentmods.dev/instructions/dsebastien/obsidian-cli-rest/agents-md"><img src="https://agentmods.dev/badge/instructions/dsebastien/obsidian-cli-rest/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.08788 | $0.08788 |
| Opus 5 | $0.04394 | $0.04394 |
| Sonnet 5 | $0.01758 | $0.01758 |
| Haiku 4.5 | $0.00879 | $0.00879 |
Grade A, and why
obsidian-cli-rest 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 4d 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.
This is a copy
94% identical to obsidian-transcriber AGENTS.md — 51 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 733 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Documentation
Documentation surfaces
Three locations, do not mix them:
README.md— GitHub landing page; pitch, features, install, quick start.docs/— end-user guide, published via GitHub Pages (Jekyll).documentation/— technical documentation for you and coding agents (architecture, domain model, business rules, history, plans).
Project overview
- Target: Obsidian Community Plugin (TypeScript → bundled JavaScript).
- Entry point:
main.tscompiled tomain.jsand loaded by Obsidian. - Required release artifacts:
main.js,manifest.json, and optionalstyles.css.
Agent Workflow
Session-start checklist
Before making any change, read these in order:
documentation/Business Rules.md— mandatory invariants (see below).- The most recent
documentation/history/yyyy-mm-dd.mdfile — what was last done and any open blockers. - Active plans under
documentation/plans/— what the current direction is. - Relevant sections of
node_modules/obsidian/obsidian.d.tswhenever you are about to use an Obsidian API you have not recently used. Do not guess API shapes; they change between versions.
Definition of done
A change is only "done" when all of the following hold:
bun run tscpasses with zero errors.bun run lintpasses with zero warnings (the repo is configured with--max-warnings 0).bun testpasses; new logic has new.spec.tscoverage next to the file it tests.bun run buildcompletes without errors.- The day's file in
documentation/history/has been updated with what was done, decisions made, and any open questions. - If a plan in
documentation/plans/drove the work, it has been updated or closed. - Any user-visible change to behavior, commands, or settings is reflected in
README.mdand/ordocs/.
You cannot self-verify UI behavior — Obsidian is a GUI app and agents do not have a live vault. State explicitly in your final message when a change requires manual runtime verification and what to check. Do not claim a UI feature "works" based solely on a passing build.
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.
- 4d ago First seen · 733 lines · 8,788 tokens per session scan A 670b1f26e047
obsidian-cli-rest AGENTS.md is an instructions file published in the GitHub repository dsebastien/obsidian-cli-rest (16 stars, last pushed 4d ago), licensed MIT. It adds 8,788 tokens to every session, about $0.0439 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to obsidian-transcriber AGENTS.md, differing in 51 lines, and is treated as a copy.
Other instructions, from other repositories
ObsidianMCPServer CLAUDE.md
Instructions for otaviocc/ObsidianMCPServer, covering claude.md, common development commands, building and testing, installation options and runtime configuration.
mcp-obsidian-via-rest CLAUDE.md
Instructions for OleksandrKucherenko/mcp-obsidian-via-rest, covering claude.md, project overview, development commands, building and running and install dependencies.
mcp-obsidian-via-rest AGENTS.md
Instructions for OleksandrKucherenko/mcp-obsidian-via-rest, a project described as: MCP Server connected to Obsidian Vault with Local REST API. (re-write it completely with BUN to make it faster and more lightweight).
ida-pro-mcp CLAUDE.md
Instructions for mrexodia/ida-pro-mcp, covering claude.md, what this project is, core implementation rules, ida thread safety and api conventions.
tableau-mcp CLAUDE.md
Claude Code instructions for tableau/tableau-mcp, covering claude.md, build & development commands, building, running the server and testing.
anytype-mcp CLAUDE.md
Instructions for anyproto/anytype-mcp, covering claude.md, common commands, development, testing and code quality.