Borrowing it
Nothing to install: this file belongs to aud1ence/obsidian-wiki-mcp. 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/aud1ence/obsidian-wiki-mcp/master/AGENTS.mdgit clone --depth 1 https://github.com/aud1ence/obsidian-wiki-mcpWrote 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/aud1ence/obsidian-wiki-mcp/agents-md)<a href="https://agentmods.dev/instructions/aud1ence/obsidian-wiki-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/aud1ence/obsidian-wiki-mcp/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.1 | $0.00815 | $0.00815 |
| Opus 5 | $0.00407 | $0.00407 |
| Sonnet 5 | $0.00163 | $0.00163 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade A, and why
obsidian-wiki-mcp 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 8d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
src/contains all TypeScript source code.src/index.tsis the MCP server entry point;src/config.tshandles config resolution.src/lib/contains core services (vault,index_manager,backlink_index,log_manager).src/tools/contains MCP tool implementations (wiki_*.ts) and tool registration insrc/tools/index.ts.test/has the custom integration test runner (runner.js) and MCP test client (mcp-client.js).dist/is build output only; do not edit generated files directly.docs/holds user/developer documentation.
Build, Test, and Development Commands
- Use
rtkas the command prefix for shell execution in this repository. rtk npm run dev: run server from source viatsxfor local development.rtk npm run build: compile TypeScript (src/) todist/.rtk npm run start: run the built server fromdist/index.js.rtk npm test: run integration tests against a spawned MCP server.rtk npm run lint: run ESLint onsrc/.rtk npm run format: run Prettier formatting onsrc/.
Coding Style & Naming Conventions
- Language: TypeScript (
strictmode, ES2022/NodeNext). - Formatting: Prettier (
tabWidth: 2,printWidth: 100, semicolons on, double quotes). - Linting: ESLint with
@typescript-eslintrecommended rules. anyis disallowed; unused args must be prefixed with_.consoleusage is restricted toconsole.error.- New tools should follow
src/tools/wiki_<name>.tsnaming.
Testing Guidelines
- Tests are integration-focused and executed by
node test/runner.js. - Add coverage for every behavior change, especially tool I/O shape and side effects.
- Keep test names descriptive by behavior (e.g., “wiki_reindex handles missing frontmatter”).
- Run
rtk npm run build && rtk npm testbefore opening a PR.
Commit & Pull Request Guidelines
- Follow conventional-style commits used in history:
feat: ...,fix: ...,docs: ...,chore: ...,refactor: ...,release: .... - Keep one logical change per PR, targeting
masterfromfeature/<name>. - PRs should include: summary, linked issue (
Closes #<id>when applicable), testing notes, and docs updates for contract changes. - For tool contract changes, clearly call out schema/output impacts and migration risk.
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.
- 8d ago First seen · 61 lines · 815 tokens per session scan A 9c4e48e0d5d0
obsidian-wiki-mcp AGENTS.md is an instructions file published in the GitHub repository aud1ence/obsidian-wiki-mcp (1 stars, last pushed 4mo ago), licensed MIT. It adds 815 tokens to every session, about $0.0041 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-31.
Other instructions, from other repositories
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.