Borrowing it
Nothing to install: this file belongs to uninhibited-scholar/obsidian-loop-wiki. 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/uninhibited-scholar/obsidian-loop-wiki/main/AGENTS.mdgit clone --depth 1 https://github.com/uninhibited-scholar/obsidian-loop-wikiWrote 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/uninhibited-scholar/obsidian-loop-wiki/agents-md)<a href="https://agentmods.dev/instructions/uninhibited-scholar/obsidian-loop-wiki/agents-md"><img src="https://agentmods.dev/badge/instructions/uninhibited-scholar/obsidian-loop-wiki/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/uninhibited-scholar/obsidian-loop-wiki/agents-md"><img src="https://agentmods.dev/badge/instructions/uninhibited-scholar/obsidian-loop-wiki/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.00768 | $0.00768 |
| Opus 5.5 | $0.00307 | $0.00307 |
| Sonnet 5.5 | $0.00154 | $0.00154 |
| Haiku 4.5 | $0.00077 | $0.00077 |
Grade A, and why
obsidian-loop-wiki 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 2mo 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — obsidian-loop-wiki
Drop this file in your project root so Codex CLI, Gemini CLI, or any agent that reads an instructions file follows the same loop as the Claude Code skill. (Claude Code users: run
./install.shinstead — it installs the richer skill version.)
You maintain an Obsidian knowledge base as a verifiable loop. Raw material goes in; you compile it into typed, cross-linked nodes that form a graph, and every run leaves an audit trail. The point of the discipline below is that an agent told to "just organize my notes" produces AI-generated clutter — drifting names, orphan pages, unsourced claims. The loop prevents that.
Locate the vault first
The vault path is in the WIKI_PATH environment variable. Never guess it.
echo "$WIKI_PATH" && ls "$WIKI_PATH"
If WIKI_PATH is unset, ask the user for their vault path. If the path has no
SCHEMA.md, it's uninitialized — scaffold it from templates/ before doing
anything. Otherwise read SCHEMA.md, index.md, log.md first; SCHEMA.md's
rules override your instincts.
Node types (keep separated)
raw/— sources. Append-only, read-only. Never edit originals.concepts/— durable ideas recurring across sources.entities/— tools, people, companies, projects.comparisons/— "X vs Y" pages that accrete over time.queries/— answers worth keeping.moc/— Maps of Content (reading routes, not listings).drafts/— outputs.
Ingest an article / organize the inbox
- Read the source; extract core themes. Do not modify originals.
- Create/update the right typed nodes per
SCHEMA.md. - Cross-link with
[[wikilinks]]— every new node links to ≥1 existing node. An orphan node is a failed run. This single rule is what makes a graph exist instead of a pile of islands. - Cite sources:
(source: raw/articles/<file>.md). - Flag inferences/unconfirmed claims as
待验证(to-verify). Never launder a guess as fact. - Update
index.md(notable nodes) and the relevantmoc/map. - Append a dated
log.mdentry: source, files created/updated, to-verify items. - Run the verification pass below and report exactly what you created/updated. If unsure where something belongs, stop and ask — a wrong classification pollutes the graph silently.
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.
- 2mo ago First seen · 68 lines · 768 tokens per session scan A 797ed0e87428
obsidian-loop-wiki AGENTS.md is an instructions file published in the GitHub repository uninhibited-scholar/obsidian-loop-wiki (2 stars, last pushed 4mo ago), licensed MIT. It adds 768 tokens to every session, about $0.0031 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-31.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.