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/uphy/obsidian-reminder/obsidian-e2enpx skills add uphy/obsidian-reminder --skill obsidian-e2egit clone --depth 1 https://github.com/uphy/obsidian-reminderWrote 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/uphy/obsidian-reminder/obsidian-e2e)<a href="https://agentmods.dev/skills/uphy/obsidian-reminder/obsidian-e2e"><img src="https://agentmods.dev/badge/skills/uphy/obsidian-reminder/obsidian-e2e.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.00140 | $0.06733 |
| Opus 5 | $0.00070 | $0.03367 |
| Sonnet 5 | $0.00028 | $0.01347 |
| Haiku 4.5 | $0.00014 | $0.00673 |
Grade A, and why
obsidian-e2e 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 5d 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 — 499 lines — stays where its author put it; the contents beside it link to each section on GitHub.
obsidian-e2e: automated testing against a live Obsidian
Relationship to manual-verify
manual-verify prepares a test vault (symlink, settings, fixture notes) and then
hands the user a checklist to click through by hand. This skill instead drives that
same running Obsidian over CDP so an agent can fire reminders, click UI, and read
back internal state without a human in the loop.
They are complementary, not interchangeable:
- Things this skill can verify automatically: reminder firing timing, toast
contents, button clicks and their effect on the file, settings state,
Reminders/ReminderNotifierinternal state. - Things only a human can verify (see "What cannot be automated" below): the look and feel of macOS system notifications, whether a system notification click actually does the right thing, and anything that depends on the user's macOS notification style settings (Banners vs. Alerts, etc).
For anything touching src/plugin/ or src/ui/, prefer running both: this skill
for the parts it can check unattended, manual-verify for the rest.
The absolute safety requirement
This machine typically has several vaults registered and multiple open at once. Only a vault explicitly and physically marked as safe for testing (see "The actual guard" below) may ever be touched. Every other vault — personal or work — must never be written to, and, per the incident below, not even read.
The wrong-vault write incident (read this before changing any guard)
Earlier in this skill's development, a guard was verified by actually calling
app.vault.adapter.write(...) with OBSIDIAN_TEST_VAULT_NAME pointed at a real,
non-test vault, on the reasoning that "the guard should reject this." It did
not. The guard at the time only checked that the vault name in the CDP page
title was unambiguous and matched what the in-page code re-read from
app.vault.getName() — and a real vault's actual name is, by definition, a
perfectly real, unambiguous, matching vault name. The write silently succeeded,
creating a stray file in a real personal vault, which then had to be cleaned up.
What ships with it
8 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.
- scripts/lib/cdp-pages.mjs 1.4 KB runs code
- scripts/lib/vault-window.mjs 5.0 KB runs code
- scripts/obsidian-eval.mjs 9.7 KB runs code
- scripts/obsidian-launch.sh 6.9 KB runs code
- scripts/obsidian-shot.sh 5.8 KB runs code
- scripts/obsidian-wait.sh 2.6 KB runs code
- scripts/reminder-fire-rewrite.mjs 2.6 KB runs code
- scripts/reminder-fire.sh 4.2 KB runs code
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.
- 5d ago First seen · 499 lines · 140 tokens per session scan A 278cc906daea
obsidian-e2e is a skill published in the GitHub repository uphy/obsidian-reminder (657 stars, last pushed 3d ago), licensed MIT. It adds 140 tokens to every session and 6,733 once invoked, about $0.0007 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
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
run-integration-tests
Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.
cli-e2e-testcase-writer
Use when adding or updating Go CLI E2E coverage for one tests/clie2e/{domain} domain of the compiled lark-cli, especially when the work requires live --help or schema exploration, scenario-based clie2e.RunCmd workflows, and per-domain coverage.md maintenance.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
harness-test-writer
Add regression test cases to the Bifrost provider harness (the Postman collection run via make run-provider-harness-test) based on a merged PR or a GitHub issue. Fetches the PR/issue, traces the affected wire path in the codebase, checks existing harness coverage, designs cases following harness conventions, inserts…
agent-device-evidence
Records iOS/Android native MP4 evidence for test/repro flows extracted from an Expensify GitHub PR or issue. Use when the user asks to "record the flow for PR.