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 skills/msinclair25/mdevolved/owd-obsidian-mindnpx skills add msinclair25/mdevolved --skill owd-obsidian-mindgit clone --depth 1 https://github.com/msinclair25/mdevolvedWhat 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.00100 | $0.01220 |
| Opus 5 | $0.00050 | $0.00610 |
| Sonnet 5 | $0.00020 | $0.00244 |
| Haiku 4.5 | $0.00010 | $0.00122 |
Grade A, and why
owd-obsidian-mind 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 yesterday.
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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MDevolved + Obsidian Mind
Legacy compatibility path. New setups should use
mdevolved-obsidian-mind; keep this pack for existingowdMCP entries and receipts.
Keep one universal MDevolved server. Apply this profile as client-side conventions; never change MCP framing, OAuth, or tool schemas for Obsidian Mind.
Confirm the runtime
- Read
vault-manifest.json. - Continue only when
templateequalsobsidian-mind. - Read
AGENTS.mdandCLAUDE.md. - Preserve the existing
.mcp.jsonentries. Add MDevolved besideqmdorom; never replace or proxy them.
Use these distinct roles:
- MDevolved: remote OAuth boundary, exact Project UUID, owner approval, current Work Packet, provenance, Decisions, Artifacts, and handoffs.
- Obsidian Mind
om: local graph search, scoped recall, reasoning, and owner-authorized capture. - MDevolved Sync: Markdown transport. Do not use it to distribute Obsidian Mind scripts, hooks, settings, or other executable runtime files.
Connect or resume
Read .owdignore first. When present, call resume_project with its exact
Project UUID and complete context policy. Never use .om-project, a folder
name, or a display label as MDevolved authority.
In a fresh session, the writer role is unconfirmed until resume_project
returns the current localVaultAccess.role. Never infer that a restarted
session lost or retained primary status from chat history, session labels, or
Mind tool availability. Treat MDevolved resume project and the legacy phrase
OWD resume project as the same direct request to run
this receipt-based resume; do not reconnect or request new authorization.
When no receipt exists, call open_project with the Project name the user
gave. Do not ask the user to copy a prompt, reconnect, or choose New versus
Existing before MDevolved reports that choice is genuinely required.
For a new Project:
- use
documentationPlan.decision = "keep-current-locations"; - keep Obsidian Mind notes in their native folders rather than moving them to
docs/; - choose the narrowest relevant concrete roots from
work/active,work/archive,work/incidents,work/1-1,org/people,org/teams,perf/brag,perf/evidence,perf/competencies,brain, andreference; - never widen
perf/h*-*/to all ofperf/; the automatic remote profile drops dynamic folder globs, so ask the owner to add an exact needed cycle such asperf/h2-2026plus every other intended root tomcp_exposed_roots, which replaces the derived root list; and - use exact source note paths.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 104 lines · 100 tokens per session scan A 1612b85d80ce
owd-obsidian-mind is a skill published in the GitHub repository msinclair25/mdevolved (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 100 tokens to every session and 1,220 once invoked, about $0.0005 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-01.
Other skills, from other repositories
backups
Use when designing or auditing a backup-and-restore program that must survive a real disaster: setting defensible RPO/RTO targets, laying out 3-2-1-1-0 copies that are offsite and immutable, wiring point-in-time recovery, and proving restores work on a schedule. NOT tuning Postgres internals or writing the…
tfw-identity
Внутренний fail-closed механизм профилей и локальной привязки Assisted; отделяет участника, роли, task owner и роль ИИ.
tfw-handoff
Command /tfw-handoff executes an approved Trace-First Workflow TS and creates ONB, implementation changes, evidence, and RF. Use for /tfw-handoff or implementation of an approved TFW task or phase.
tfw-init
Command /tfw-init initializes Trace-First Workflow or attaches and repairs TFW tooling in an existing project. Use for /tfw-init, first-time setup, project discovery, adapter installation, or Codex adapter repair.
tfw-knowledge
Command /tfw-knowledge consolidates Trace-First Workflow Fact Candidates into verified project knowledge. Use for /tfw-knowledge, the knowledge gate, fact promotion, topic files, or knowledgestate.yaml maintenance.
tfw-review
Command /tfw-review reviews a completed Trace-First Workflow RF against its TS, implementation, and evidence. Use for /tfw-review, a TFW verdict, RF verification, or a REVIEW artifact.