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/benoror/obsidianos_work/note-statusnpx skills add benoror/obsidianos_work --skill note-statusgit clone --depth 1 https://github.com/benoror/obsidianos_workWrote 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/benoror/obsidianos_work/note-status)<a href="https://agentmods.dev/skills/benoror/obsidianos_work/note-status"><img src="https://agentmods.dev/badge/skills/benoror/obsidianos_work/note-status.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.00038 | $0.01800 |
| Opus 5 | $0.00019 | $0.00900 |
| Sonnet 5 | $0.00008 | $0.00360 |
| Haiku 4.5 | $0.00004 | $0.00180 |
Grade A, and why
note-status 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Note Status
Usage
/note-status <path>— Check processing status of a specific meeting note./note-status [dates]— Check all meeting notes matching a date filter./note-status all— Check every meeting note in the vault./note-status(no args) — Defaults tothis week./note-status pending [dates] [--step=<step>]— Filter to actionable pending notes and prompt the user to select which ones to act on. See Pending Mode.
Processing Checklist
A meeting note is fully processed when all four frontmatter properties are present:
| Step | Property | Set by | Requires |
|---|---|---|---|
notes |
Notes: with URLs (not empty/absent) |
User or /cache-notes prompt |
— |
cache |
NotesCached: |
/cache-notes |
notes with a supported provider URL |
participants |
Participants: |
/fill-participants |
— |
todos |
TodosExtracted: |
/followup-todos |
— |
A note is pending when any of these are missing.
Detection Rules
Notes:counts as missing if the property is absent, empty, or contains no URLs.NotesCached:counts as missing if absent. Presence of the timestamp (any value) means cached.Participants:counts as missing if absent. Presence (even—) means filled.TodosExtracted:counts as missing if absent. Presence of the timestamp means extracted.
Dependency Chain
Some steps have prerequisites. A note is actionable for a step only when the step is missing and its prerequisites are met:
| Step | Actionable when |
|---|---|
notes |
Notes: absent/empty — always actionable |
cache |
NotesCached: absent and Notes: contains at least one supported provider URL (e.g. docs.google.com). Notes with only unsupported URLs (e.g. Otter-only) are not actionable for caching. |
participants |
Participants: absent — always actionable |
todos |
TodosExtracted: absent — always actionable |
The dependency chain matters for --step filtering (see Pending Mode) and for the status table, where a step can be shown as ❌ (missing but actionable), ⏸️ (missing, blocked by prerequisite), or ✅ (done).
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 · 141 lines · 38 tokens per session scan A 669231eee465
note-status is a skill published in the GitHub repository benoror/obsidianos_work (166 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 1,800 once invoked, about $0.0002 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
markdown
Documentation and content creation standards.
ledger-import-fixture-replay
Use when replaying Ledger import CSV fixtures to verify sourceRef preservation, cent normalization, and deterministic posting dates.
plannotator-compound
Analyze a user's Plannotator plan archive to extract denial patterns, feedback taxonomy, evolution over time, and actionable prompt improvements — then produce a polished HTML dashboard report. Falls back to Claude Code ExitPlanMode denial reasons when Plannotator data is unavailable.
plannotator
Reference for using the Plannotator CLI: plan review, code review, annotating files, URLs, folders, and running local apps, annotating the last assistant message, browsing archived plan decisions, and exporting or sharing Guided Reviews. Invoke when asked to use Plannotator for anything not covered by a more specific…
plannotator-annotate
Open Plannotator's annotation UI for a file, folder, or URL, then address the returned annotations.
obsidian-cli
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their…