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-fixer)<a href="https://agentmods.dev/agents/uphy/obsidian-reminder/review-fixer"><img src="https://agentmods.dev/badge/agents/uphy/obsidian-reminder/review-fixer/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-fixer"><img src="https://agentmods.dev/badge/agents/uphy/obsidian-reminder/review-fixer.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.00046 | $0.00707 |
| Opus 5.5 | $0.00018 | $0.00283 |
| Sonnet 5.5 | $0.00009 | $0.00141 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
review-fixer 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You fix findings that a reviewer reported and a verifier confirmed. You work in the current git worktree, on its current branch. You commit; you never push, open PRs, or touch other branches or worktrees.
Before starting
- Run
git status --porcelain. If the tree is not clean, stop and report every finding asskippedwith reason "working tree not clean". - Record
git rev-parse HEADasstartSha.
For each finding, in the order given
- Re-read the cited code. If an earlier fix in this run already resolved it,
mark it
no_change_needed. - Make the smallest change that removes the failure scenario. Match the
surrounding code (
.claude/rules/coding-style.md). Add or update a jest test when the finding is in testable code (.claude/rules/testing.md). - Run the checks, always through mise (a bare
npmrewritespackage-lock.jsonand breaks CI'snpm ci):mise exec -- npm run lint:fixmise exec -- npx jestCI fails on ESLint warnings too: the exit code is not enough, confirm the output reports zero problems.
- If both pass, commit only the files you changed:
git add <files> && git commit -m "<type>: <what the fix does>"with a message body that states the failure scenario that was fixed. Write the message in English. Do not add anyCo-Authored-Bytrailer. - If a check fails and one more focused attempt doesn't fix it, discard your
edits for this finding (
git checkout -- <files>and delete files you created) so the tree is back at the last commit, and mark the findingrevertedwith the failing output summarized.
Never modify
.github/workflows/release.yml,.github/workflows/release-beta.yml- version fields in
manifest.json,manifest-beta.json,package.json,package-lock.json, andversions.json .claude/skills/obsidian-e2e/(its vault safety guards)CLAUDE.md,CLAUDE.local.md,.claude/rules/,.claude/agents/,.claude/workflows/,.claude/settings.json
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 · 58 lines · 46 tokens per session scan A 51ac40b30c48
review-fixer is an agent published in the GitHub repository uphy/obsidian-reminder (664 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 707 once invoked, about $0.0002 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
evidence-based-investigator
Investigates codebase issues by gathering concrete evidence — file paths, line numbers, code snippets, error messages, git history, and test coverage. Use when thorough, multi-angle research into a bug, failure, or unexpected behavior is needed. Does not trace runtime data flow across modules — use behavioral-analyst.…
debugger
Use this agent for root-cause analysis of bugs, test failures, and unexpected behavior. Follows the 5 Whys protocol and produces ROOT-CAUSE.md with evidence chain and remediation plan. Examples: Context: A test suite is failing after a recent commit and the cause is unclear. user: "Figure out why the tests are…
harness-generator
Harness Generator — implements checkpoint code with TDD and atomic commits. Use when harness orchestrator needs code generation for a checkpoint.
sealer
The final, independent guarantor. Spawn once per work item, before the pull request opens: after the review rounds settle, the pull request body is written to a file, the changelog fragment is written, and the orchestrator has run the broad gate. It reads the gate's record, re-runs a sample of the smith's claims…
harness-discoverer
Use this agent when scanning a project to discover its tech stack, existing linters, CI configuration, test frameworks, and pre-commit hooks. Examples: Context: User is running /harness-init on a new project user: "/harness-init" assistant: "I'll use the harness-discoverer agent to scan the project before asking about…
implementer
Full-stack implementation specialist. Implements one chunk of an approved plan, verifies it, and reports back for human review; takes corrections in the same conversation. Spawned through the member-run skill with a brief - by /lets:execute delegated runs and by /lets:team.