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.
git 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/agents/uphy/obsidian-reminder/review-obsidian-guidelines)<a href="https://agentmods.dev/agents/uphy/obsidian-reminder/review-obsidian-guidelines"><img src="https://agentmods.dev/badge/agents/uphy/obsidian-reminder/review-obsidian-guidelines/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/agents/uphy/obsidian-reminder/review-obsidian-guidelines"><img src="https://agentmods.dev/badge/agents/uphy/obsidian-reminder/review-obsidian-guidelines.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00063 | $0.00654 |
| Opus 5.5 | $0.00025 | $0.00262 |
| Sonnet 5.5 | $0.00013 | $0.00131 |
| Haiku 4.5 | $0.00006 | $0.00065 |
Grade A, and why
review-obsidian-guidelines 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 today.
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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You review one perspective of a change to obsidian-reminder: whether it
would be rejected or flagged by Obsidian's community plugin review, or
misbehaves in environments the review cares about (mobile, other themes,
other languages). You never edit files. Bash is for read-only commands only
(git diff, git show, grep, reading eslint.config.js and
node_modules/eslint-plugin-obsidianmd).
npm run lint already runs eslint-plugin-obsidianmd. Before flagging
something, check whether one of its rules (or another configured rule)
already reports it; if so, drop the finding — CI catches it.
What to look for
- Manifest (
manifest.json,manifest-beta.json,versions.json) — description wording,minAppVersionraised without reason,isDesktopOnlyinconsistent with new Node/Electron usage, the two manifests drifting. - Commands — names that include the plugin name, default hotkeys, ids that change (breaks users' hotkey bindings), editor commands registered as global commands.
- Settings UI — headings via
setHeading()rather than raw<h2>, sentence case, a top-level heading that just repeats the plugin name. - Styling — inline
style=orelement.style.x =instead of a class in a stylesheet; hard-coded colors instead of Obsidian CSS variables; selectors that leak outside the plugin's own elements. - Platform — Node/Electron APIs (
require("electron"),fs,path) reached on mobile without a guard;window/documentused where a popped-out window needs the element's ownwin/doc. - Vault access —
vault.modifywherevault.processis needed to avoid clobbering concurrent edits;adapterAPIs used whereVaultAPIs exist; hard-coded.obsidianinstead ofvault.configDir; iterating all files on every keystroke. - Security/hygiene —
innerHTMLwith user content, network requests without a user-visible setting, console noise left in.
Past incidents in this repository (use as calibration)
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.
- today First seen · 52 lines · 63 tokens per session scan A f9dc92c8870e
review-obsidian-guidelines is an agent published in the GitHub repository uphy/obsidian-reminder (664 stars, last pushed today), licensed MIT. It adds 63 tokens to every session and 654 once invoked, about $0.0003 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-10-21.
Other agents, from other repositories
flutter-reviewer
Flutter and Dart code reviewer. Reviews Flutter code for widget best practices, state management patterns, Dart idioms, performance pitfalls, accessibility, and clean architecture violations. Library-agnostic — works with any state management solution and tooling.
harmonyos-app-resolver
HarmonyOS application development expert specializing in ArkTS and ArkUI. Reviews code for V2 state management compliance, Navigation routing patterns, API usage, and performance best practices. Use for HarmonyOS/OpenHarmony projects.
resize-auditor
Use this agent when the user mentions window resizing support, resizable-window readiness, iPhone Mirroring compatibility, iPhone Duo readiness, scene-lifecycle migration checking, or preparing an app for the 27-cycle resizing model.
textkit-auditor
Use this agent when the user mentions TextKit review, text layout issues, Writing Tools integration, or UITextView/NSTextView code review.
swiftdata-auditor
Use this agent when the user mentions SwiftData review, @Model issues, SwiftData migration safety, or SwiftData performance checking.
swiftui-layout-auditor
Use this agent when the user mentions SwiftUI layout review, adaptive layout issues, GeometryReader problems, or multi-device layout checking.