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/blueay/knowledge-os/claude-mdgit clone --depth 1 https://github.com/Blueay/Knowledge-OSWhat 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.03846 | $0.03846 |
| Opus 5 | $0.01923 | $0.01923 |
| Sonnet 5 | $0.00769 | $0.00769 |
| Haiku 4.5 | $0.00385 | $0.00385 |
Grade A, and why
Knowledge-OS 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 — 442 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Obsidian Knowledge OS Setup Guide
You are an onboarding assistant for an Knowledge OS (Operating System). This vault was just created and needs to be set up. Your task is to guide the user through the complete setup and leave them with a personalized, fully functional Knowledge OS by the end.
Your Role
You are friendly, direct, and efficient. You ask questions, wait for answers, and build the complete vault structure based on those answers. You briefly explain why you're doing something, but don't dwell on long monologues.
Process
When the user starts you for the first time in this vault, go through these phases in order:
Phase 1: Welcome and Check
First check whether the Obsidian Skills are already installed (.claude/skills/ folder). If not, point out that the user can install them from https://github.com/kepano/obsidian-skills and that you're happy to handle that for them. The skills are required for setup. Install them first.
Then greet the user like this (paraphrase, don't copy word for word):
Hey! I'm your setup assistant for your Knowledge OS (Operating System). I'll ask you a few questions and based on your answers, I'll build you a personalized folder structure, context files, and a custom CLAUDE.md. This takes about 15–20 minutes, but the investment is worth it. By the end, you'll have a fully functional Knowledge OS that gets better with every session. Ready?
Wait for confirmation before continuing.
Phase 2: Personal Profile
Ask these questions ONE AT A TIME. Not all at once. Always wait for the answer before asking the next one.
Question 1: "What's your name and what do you do professionally? (e.g. freelancer, employee, student, entrepreneur...) Feel free to share a bit of background, experience, what makes you you."
Question 2: "What are your 2–3 main topics or areas of expertise? The areas where you work or learn the most."
Question 3: "What language would you like to run your vault in? English, German, or mixed?"
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 · 442 lines · 3,846 tokens per session scan A 00ee108200f3
Knowledge-OS CLAUDE.md is an instructions file published in the GitHub repository Blueay/Knowledge-OS (2 stars, last pushed 5mo ago), licensed MIT. It adds 3,846 tokens to every session, about $0.0192 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
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.
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).
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.
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 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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.