Borrowing it
Nothing to install: this file belongs to evielync/hyo-claude-code-obsidian-plugin. 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/evielync/hyo-claude-code-obsidian-plugin/main/CLAUDE.mdgit clone --depth 1 https://github.com/evielync/hyo-claude-code-obsidian-pluginWrote 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/evielync/hyo-claude-code-obsidian-plugin/claude-md)<a href="https://agentmods.dev/instructions/evielync/hyo-claude-code-obsidian-plugin/claude-md"><img src="https://agentmods.dev/badge/instructions/evielync/hyo-claude-code-obsidian-plugin/claude-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.00685 | $0.00685 |
| Opus 5 | $0.00342 | $0.00342 |
| Sonnet 5 | $0.00137 | $0.00137 |
| Haiku 4.5 | $0.00068 | $0.00068 |
Grade A, and why
hyo-claude-code-obsidian-plugin CLAUDE.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 2d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hyo — working rules
Hyo is a public Obsidian plugin. Other people run it, on their machines, and they cannot read the code to work out why something is broken.
Every platform, every time
Hyo runs on macOS, Windows, Linux, iOS and Android. Every change is thought through on all of them before it ships, not just the one it was written on.
The places this breaks are always the same, so check them first:
| Thing | What to hold |
|---|---|
| Locating a binary | Never a hardcoded list of Unix paths. Include the Windows install locations and read them from ProgramFiles / LOCALAPPDATA so a non-default drive still resolves. |
Building PATH |
Join with path.delimiter, never ":". The extra Unix directories are Mac and Linux only. |
| Joining paths | path.join, never string concatenation with /. |
| Running a shell command | The osascript wrapper is macOS-only and exists because the App Store Tailscale binary lies about its exit code. Every other platform spawns directly. |
Anything under Platform.isMobile |
Node built-ins do not exist on mobile. They are deferred at the top of each module for this reason. |
Mobile access shipped in 0.5.0 having never been considered on Windows, and was broken there for everyone until 31 August. The binary lookup listed four paths and all four were Mac or Linux. That is the shape of this mistake: it is invisible on the machine you are building on.
Failures must say what happened
A status a person cannot act on is worse than a crash. Anything that can fail while someone waits has to end in a stated reason.
- No unbounded waits. Every spawned process gets a timeout, and a hung one is reported as a failure like any other.
- No swallowed errors. A
catchthat keeps a queue alive must still surface what it caught. A chain that stops halfway leaves the UI saying nothing forever. - Async work needs its own catch. A try/catch around a call that returns a promise only covers the synchronous part. Everything after the first
awaitneeds catching where it runs. - Log where a member can reach it. The developer console is not somewhere anyone will look. Mobile startup writes to
~/.hyo/mobile.logregardless of the debug setting. - Error text names the cause and the next step. "Tailscale isn't installed" when it plainly is installed sends people off to fix the wrong thing, and the report never comes back.
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.
- 2d ago First seen · 40 lines · 685 tokens per session scan A 01b9b508189d
hyo-claude-code-obsidian-plugin CLAUDE.md is an instructions file published in the GitHub repository evielync/hyo-claude-code-obsidian-plugin (21 stars, last pushed 3d ago), licensed MIT. It adds 685 tokens to every session, about $0.0034 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-09-04.
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.