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 skills add alexeyshishin/as-skill --skill obsidian-inbox-reviewgit clone --depth 1 https://github.com/alexeyshishin/as-skillWrote 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/alexeyshishin/as-skill/obsidian-inbox-review)<a href="https://agentmods.dev/skills/alexeyshishin/as-skill/obsidian-inbox-review"><img src="https://agentmods.dev/badge/skills/alexeyshishin/as-skill/obsidian-inbox-review/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/skills/alexeyshishin/as-skill/obsidian-inbox-review"><img src="https://agentmods.dev/badge/skills/alexeyshishin/as-skill/obsidian-inbox-review.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.01035 |
| Opus 5 | $0.00032 | $0.00517 |
| Sonnet 5 | $0.00013 | $0.00207 |
| Haiku 4.5 | $0.00006 | $0.00103 |
Grade A, and why
obsidian-inbox-review 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 12d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
obsidian-inbox-review
Read-only, report only. Files are not modified. The output is a structured list of recommendations.
Vault structure, tags, and frontmatter — in .claude/rules/ (vault-struct.md, tags.md, note-types-frontmatter.md).
Triggers: "go through the inbox", "inbox review", "what's in my inbox", "help with #inbox/review", "review my notes".
Algorithm
1. Scan
# All notes in the inbox, by modification date (oldest first)
ls -t "00. Входящие/" | tac
# Only notes tagged #inbox/review
rg -l "#inbox/review" "00. Входящие/"
2. Analyze each note (no changes!)
- Read the content
- Determine the main topic (one note = one topic)
- Check links: are there wikilinks, is it mentioned in any MOC
- Decide on the category
- Formulate a recommendation
3. Categorization
Pick the structural tag and folder per .claude/rules/tags.md (the "Structural tags" section). Summary decision table:
| What's in the note | Tag | Folder |
|---|---|---|
| Atomic thought / concept | #thought |
03. Ресурсы/<Тема>/База знаний/ |
| Map / navigation | #moc |
02. Сферы/07. Карты/ |
| Person | #person |
No folder currently exists — ask the user where it should live |
| Book / article / video | #book / #article / #video |
03. Ресурсы/<Тема>/<Источник>/ — one subfolder per source |
| Project | #project |
01. Проекты/<Проект>/ |
| Meeting / 1:1 | #meeting |
02. Сферы/02. Работа/ |
| Conference notes | #conference |
No folder currently exists — ask the user where it should live |
| Journal / reflection | #journal/daily |
05. Дневник/ (flat, filename DD-MM-YYYY.md) |
| Content for a channel | + #telegram or #content |
02. Сферы/04. Личный блог/ |
| No longer relevant | #archive |
04. Архив/ |
| Duplicate | — | merge or flag |
4. Prioritization
Process in this order:
- Notes with an explicit wikilink to active projects
- Notes with
TODO/#inbox/action - Recent ones (last 7 days)
- Old ones with no links (often archive candidates)
What ships with it
1 file 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.
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.
- 12d ago First seen · 108 lines · 63 tokens per session scan A 0a7b4edee0d6
obsidian-inbox-review is a skill published in the GitHub repository alexeyshishin/as-skill (4 stars, last pushed 23d ago), licensed MIT. It adds 63 tokens to every session and 1,035 once invoked, about $0.0003 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-31.
Other skills, from other repositories
behavior-design
Use when a goal must be converted into a repeatable behavior, cue, SOP, review cadence, and identity-aligned reinforcement.
daily-okr
Use when planning or closing a daily knowledge-compounding cycle across input, cognition, wiki, behavior, creativity, output, and feedback.
session-manager
A fallback skill for recording development sessions and restoring project context from an Obsidian vault, a folder of linked notes. It handles explicit resume, handoff, status, and end-of-session requests when automatic capture is unavailable.
budget-continue
Show 4-option continuation prompt when session budget is low. Options: remind later (CronCreate), auto-continue locally (Desktop task), auto-continue in cloud (Cloud task), continue now. Trigger when: budget warning fires, session limit reached, context is full, user sees budget warning.
tasknotes
Manage tasks in an Obsidian TaskNotes vault. Use for creating, reading, updating, or completing tasks; checking what is open or in progress; adding items to a list; marking tasks done or in progress; updating task status or priority; investigating why a task is missing from a view or board; troubleshooting TaskNotes…
personalize
Customize this workspace to your role, company, and tools - quick (3 min) or deep (10 min).