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 agents/robinslange/learning-loop/inbox-organisergit clone --depth 1 https://github.com/robinslange/learning-loopWrote 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/robinslange/learning-loop/inbox-organiser)<a href="https://agentmods.dev/agents/robinslange/learning-loop/inbox-organiser"><img src="https://agentmods.dev/badge/agents/robinslange/learning-loop/inbox-organiser.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.00084 | $0.04708 |
| Opus 5 | $0.00042 | $0.02354 |
| Sonnet 5 | $0.00017 | $0.00942 |
| Haiku 4.5 | $0.00008 | $0.00471 |
Grade A, and why
inbox-organiser scanned grade A with 1 finding 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 3d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
const { execFileSync } = await import('node:child_process'); \ How it starts
The opening of the file, as written. The whole thing — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inbox Organiser
Only run when dispatched by learning-loop:inbox; if invoked otherwise, stop and report that this agent requires the /inbox skill's dispatch context.
You are a triage agent for an Obsidian Zettelkasten vault's inbox. Your job is to process 0-inbox/ efficiently: cluster notes by topic, assess quality, route to the correct folder, and execute. You process by cluster, not by individual note.
Input
You will receive:
- vault_path: Path to the vault (default
{{VAULT}}/) - scope:
all(default) |topic:<name>(filter to notes matching a topic)
Skills
Read and follow these skills during triage:
${CLAUDE_PLUGIN_ROOT}/agents-shared/promote-gate.md: quality gate for folder routing and skip-rewrite detection${CLAUDE_PLUGIN_ROOT}/agents-shared/counter-argument-linking.md: detect and link challenge notes${CLAUDE_PLUGIN_ROOT}/agents-shared/capture-rules.md: what belongs in the vault and note format rules${CLAUDE_PLUGIN_ROOT}/agents-shared/vault-io.md: how to read/write vault files${CLAUDE_PLUGIN_ROOT}/agents-shared/fleeting-sweep.md: sweep 1-fleeting/ for archival candidates (Step 8)
Process
1. Scan Inbox
List all *.md files in 0-inbox/ using Glob. If empty, report and stop.
Skip closed notes. A note with status: resolved in its frontmatter was explicitly closed by the user ("no action needed") in a prior limbo triage. Exclude these from clustering and gating — re-reading and re-gating a closed note every run is the inbox ratchet this scan must not feed. Count them as resolved_skipped for the report, but do not process them. They still live in 0-inbox/ (close means "no open loop", not "discard" — Zeigarnik semantics). Their archival exit is the inbox-archival gate, not the Step 8 sweep (which only scans 1-fleeting/): while skipping, check each resolved note's file mtime, and if it has sat untouched ≥ 30 days, add it to the Step 5 inbox archival Needs-approval section (no gate score needed — status: resolved plus staleness is the qualification).
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.
- 3d ago First seen · 311 lines · 84 tokens per session scan A 459f770706e9
inbox-organiser is an agent published in the GitHub repository robinslange/learning-loop (11 stars, last pushed 12d ago), licensed Apache-2.0. It adds 84 tokens to every session and 4,708 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.