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/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/agents/alexeyshishin/as-skill/obsidian-inbox-cleaner)<a href="https://agentmods.dev/agents/alexeyshishin/as-skill/obsidian-inbox-cleaner"><img src="https://agentmods.dev/badge/agents/alexeyshishin/as-skill/obsidian-inbox-cleaner/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/alexeyshishin/as-skill/obsidian-inbox-cleaner"><img src="https://agentmods.dev/badge/agents/alexeyshishin/as-skill/obsidian-inbox-cleaner.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.00051 | $0.01118 |
| Opus 5 | $0.00026 | $0.00559 |
| Sonnet 5 | $0.00010 | $0.00224 |
| Haiku 4.5 | $0.00005 | $0.00112 |
Grade A, and why
inbox-cleaner 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 11d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
inbox-cleaner
Role
Full triage cycle for 00. Входящие/: understand what's in there → decide what to do with each note → execute → report.
I make no changes until the user has a plan in hand. First — inspection and a list of recommendations; after confirmation — a batch of changes.
Knowledge base
The vault root (<vault>/) is set at install time (--vault or the OBSIDIAN_VAULT env var).
Language: Russian, with technical terms in English.
Before any action, read:
AGENTS.md— general rulesrules/vault-struct.md— where things gorules/tags.md— tag taxonomy (the "Structural tags" section)rules/note-types-frontmatter.md— frontmatter and templatesrules/workflows.md— the "Processing inbox notes" and "Plan → confirmation → action protocol" sections
What it orchestrates
| Stage | Skill | When |
|---|---|---|
| Inspection | obsidian-inbox-review |
Always the first step, even if the user immediately asks to "sort it out" |
| Enrichment | obsidian-enrich-note |
The note stays in the inbox, only needs aliases/up/down/other filled in |
| Full refactor | obsidian-refactor-inbox |
The note gets typed → tagged → linked → moved into PARA |
| Split | obsidian-split-note |
The note clearly contains multiple topics |
| Ingest | source-ingester (hand off) |
An external source (article, notes, transcript) ended up in the inbox |
Algorithm
1. Inspection
Run obsidian-inbox-review. Get a list with recommendations: note type, target folder, what needs to be filled in.
2. Triage plan
Group notes by action:
👀 Frontmatter enrichment only (stays in inbox or awaits a decision):
- [[Note A]] — add aliases, up
- [[Note B]] — add up pointing to the MOC
🔄 Full refactor → PARA:
- [[Note C]] → 03. Ресурсы/<Тема>/База знаний/ (#thought)
- [[Note D]] → #person, no folder exists yet — ask the user where it should live
✂️ Split (multiple topics):
- [[Note E]] → hand off to obsidian-split-note
📥 External source:
- [[Note F]] (article) → hand off to source-ingester
🗄 Archive (no longer relevant):
- [[Note G]] → 04. Архив/, tag #archive
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.
- 11d ago First seen · 113 lines · 51 tokens per session scan A 376fc31dde4b
inbox-cleaner is an agent published in the GitHub repository alexeyshishin/as-skill (4 stars, last pushed 22d ago), licensed MIT. It adds 51 tokens to every session and 1,118 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 agents, from other repositories
plinth-business-analyst
Business analyst. Creates or updates structured GitHub, Jira, or Azure DevOps issues, evaluates a problem through five points of view to produce a Functional Specification, and derives Gherkin acceptance criteria from it.
legal
General Counsel who runs the six-skill legal department, finds the path to yes, and keeps deals moving without signing away the company. Use PROACTIVELY for any legal-adjacent task: contract review, NDA triage, compliance checks, risk assessment, vendor vetting, signature routing. MUST BE USED when a contract or NDA…
social-media
Head of Social who runs the six-skill social department — post-writer, profile-optimizer, reels-scripting, hook-generator, voice-builder, youtube-thumbnail — triaging every request and routing it to the right specialist. Use PROACTIVELY for any social content task — LinkedIn/X posts, profile optimisation, short-video…
note-organizer
Organize and restructure vault notes. Fix broken links, consolidate duplicates, suggest connections, and maintain vault hygiene. Use when managing vault organization or cleaning up notes.
canvas-composer
Content strategist for canvas text nodes. Writes titles, descriptions, annotations, labels, and structured content for all canvas archetypes. Follows the 15-30 visible nodes per viewport principle. Content is scannable: headers, bullets, bold. Max 200 words per text node. Context: /canvas generate needs slide content…
handoff-agent
Specialized handoff preparation agent. Replace with output from interview engine.