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 skills add Ancienttwo/repo-harness --skill obsidian-memorygit clone --depth 1 https://github.com/Ancienttwo/repo-harnessWrote 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/skills/ancienttwo/repo-harness/obsidian-memory)<a href="https://agentmods.dev/skills/ancienttwo/repo-harness/obsidian-memory"><img src="https://agentmods.dev/badge/skills/ancienttwo/repo-harness/obsidian-memory/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/skills/ancienttwo/repo-harness/obsidian-memory"><img src="https://agentmods.dev/badge/skills/ancienttwo/repo-harness/obsidian-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 88 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00033 | $0.00262 |
| Opus 5.5 | $0.00013 | $0.00105 |
| Sonnet 5.5 | $0.00007 | $0.00052 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
obsidian-memory 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 19d 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.
What it actually says
obsidian-memory
Bot entrypoint. The vault is optional. Keep authority in repo artifacts;
sync direction is repo → brain. No configured brainRoot is a legitimate steady state.
The skill resolves the root fail-closed. Never guess or create one to complete a task.
The brain CLI behaves differently: it uses the environment override, then user
config, then a default root. Write commands can create directories. Do not use
that CLI fallback to resolve a vault for this skill.
Use references/worker.md for assigned recall, formatting, write and index steps.
Exclusion-first write gate: anything already recorded by Git, CI, a registry,
or a re-runnable command gets only a pointer in the vault, never a restatement.
Save only reusable reasons or methods that have one authoritative home.
Exclude secrets and transient status. Verify recalled claims against current state.
Preserve paths owned by brain-manifest.json. Hooks never read or write the vault.
An ordinary task does not require memory persistence.
What ships with it
2 files 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.
- 19d ago Changed · +3 lines 245f34ec3eff
- 20d ago Changed · -70 lines · -179 tokens per session 54d6ff470e04
- 1mo ago Changed 7f6adb89a7e7
- 1mo ago First seen · 91 lines · 212 tokens per session scan A 434ceb8d391f
obsidian-memory is a skill published in the GitHub repository Ancienttwo/repo-harness (435 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 262 once invoked, about $0.0001 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-30.
Other skills, from other repositories
agenticx-memory-architect
Guide for setting up and using the AgenticX memory system including Mem0 integration, long-term memory, context management, and memory-enhanced agents. Use when the user wants to add memory to agents, persist conversation history, build memory-aware workflows, or integrate with Mem0 for long-term recall.
continuous-attention
Use when the user asks to keep watching an external state, notify them when something changes or a condition is met, remember fresh external state across turns, or manage an existing Context Binding or Event Subscription.
codebase-memory-mcp
Resolve canonical Git checkouts, index and verify codebase-memory-mcp graphs through the guarded CLI, open its browser viewer on request, and safely audit duplicate worktree caches. Use when a user mentions codebase memory MCP, dependency graphs, searchgraph, tracepath, indexrepository, worktree indexes, or oversized…
iwe-restore
A recovery skill that restores an agent’s saved memory and instruction files from an exocortex backup when moving to a new computer or workspace. It shows what it found and asks for confirmation before copying files.
w-reflection
A recording step for storing a scored worldview reflection in a learning database. A worldview reflection is a structured review of assumptions, causes, consequences, and a person's role in a situation.
context-engineering
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.