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/davidroliverba/architectkb/opennpx skills add DavidROliverBA/ArchitectKB --skill opengit clone --depth 1 https://github.com/DavidROliverBA/ArchitectKBWrote 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/davidroliverba/architectkb/open)<a href="https://agentmods.dev/skills/davidroliverba/architectkb/open"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/open.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 | $0.00012 | $0.00692 |
| Opus 5 | $0.00006 | $0.00346 |
| Sonnet 5 | $0.00002 | $0.00138 |
| Haiku 4.5 | $0.00001 | $0.00069 |
Grade A, and why
open 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 4d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/open - Open in Obsidian
Opens a vault note in Obsidian directly from Claude Code.
Usage
/open <note name> # Open by name (fuzzy match)
/open daily # Open today's daily note
/open Concept - CAMO # Open a specific note
/open Meeting - 2026-02-11 # Open by partial name
Instructions
1. Resolve the Note
Determine what the user wants to open:
- "daily" or "today" — resolve to
Daily/YYYY/YYYY-MM-DDusing today's date - Exact filename — use as provided
- Partial name — use Glob to find the matching file:
# Find by partial name
Use the Glob tool with pattern **/*<name>*.md to find the file. If multiple matches, pick the most likely one or ask the user.
2. Build the URI Path
Convert the file path to a URI-encoded relative path (from vault root):
- Strip the vault root prefix
- Strip the
.mdextension - URL-encode spaces as
%20 - URL-encode forward slashes as
%2F
Examples:
Daily/2026/2026-02-11.md→Daily%2F2026%2F2026-02-11Concept - Context Engineering.md→Concept%20-%20Context%20EngineeringMeetings/2026/Meeting - 2026-02-11 Stand Up.md→Meetings%2F2026%2FMeeting%20-%202026-02-11%20Stand%20Up
3. Open in Obsidian
Run this command with dangerouslyDisableSandbox: true (required for inter-process communication):
open "obsidian://open?vault=BA-DavidOliver-ObsidianVault&file=<encoded_path>"
The sandbox must be disabled — the open command needs macOS Launch Services to activate Obsidian, which is blocked in sandbox mode.
4. Confirm
Tell the user which note was opened. If Obsidian is not running, the error will mention procNotFound — tell the user to start Obsidian first.
Special Cases
| Input | Resolves To |
|---|---|
daily / today |
Daily/YYYY/YYYY-MM-DD (today's date) |
yesterday |
Daily/YYYY/YYYY-MM-DD (yesterday's date) |
| A person's name | People/<Name>.md |
A type prefix (e.g. ADR - ) |
Search in the appropriate folder |
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.
- 4d ago First seen · 84 lines · 12 tokens per session scan A a81f98161776
open is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It adds 12 tokens to every session and 692 once invoked, about $0.0001 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…