Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add robinslange/learning-loop/plugin install 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/skills/robinslange/learning-loop/inbox)<a href="https://agentmods.dev/skills/robinslange/learning-loop/inbox"><img src="https://agentmods.dev/badge/skills/robinslange/learning-loop/inbox/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/robinslange/learning-loop/inbox"><img src="https://agentmods.dev/badge/skills/robinslange/learning-loop/inbox.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.00090 | $0.02537 |
| Opus 5.5 | $0.00036 | $0.01015 |
| Sonnet 5.5 | $0.00018 | $0.00507 |
| Haiku 4.5 | $0.00009 | $0.00254 |
Grade A, and why
inbox 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 1mo 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inbox: Batch Triage and Processing
Overview
Launches the inbox-organiser agent to process all notes in 0-inbox/. The agent clusters by topic, assesses maturity via the promote-gate skill, detects counter-arguments, and executes promotions autonomously. Merges, deletes, and fleeting archival require approval.
When to Use
- Inbox has accumulated notes that need triage
- After a series of
/reflectsessions that deposited notes - When the user asks to clean up, process, or triage the inbox
Provenance
This skill emits provenance events for pipeline observability. Run each Bash command silently.
At session start:
ll-run provenance-emit.js '{"agent":"inbox","skill":"inbox","action":"session-start"}'
At session end. Alongside the existing counters, include the common outcome shape: items_in (notes triaged), items_out (promoted plus merged), items_flagged (limbo), duration_ms:
ll-run provenance-emit.js '{"agent":"inbox","skill":"inbox","action":"session-end","promoted":N,"deleted":N,"merged":N,"rewrites":N,"limbo":N,"items_in":N,"items_out":N,"items_flagged":N,"duration_ms":N}'
Per-note tracking is automatic for main-thread writes via the PostToolUse hook; subagent writes and edits (note-writer files, the organiser's own Edits and mv-promotions) bypass it and are covered by the Step 2 hook replays (2a for note-writer output, 2c for the agent's touched-files inventory).
Process
Step 1: Launch Agent
Launch the inbox-organiser agent with:
- vault_path:
{{VAULT}}/ - scope:
all(ortopic:<name>if the user specified a topic filter)
The agent definition is at ${CLAUDE_PLUGIN_ROOT}/agents/inbox-organiser.md (resolve to a literal path before dispatch — see agents-shared/vault-io.md → Placeholders).
Spawn the inbox-organiser agent (dispatch: skills-shared/dispatch.md) with the full prompt from the agent definition, or launch a general-purpose agent that reads the agent file.
Step 1.5: Surface Librarian Observations for Inbox Notes
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.
- 1mo ago Changed 79ed338d9f0b
- 1mo ago Changed b981bd6cffd7
- 1mo ago Changed · -4 lines f726d8265d5d
- 1mo ago Changed · +4 lines c92b617abf4d
- 2mo ago Changed ab1fcfb8d926
- 2mo ago First seen · 133 lines · 90 tokens per session scan A fb427a450585
inbox is a skill published in the GitHub repository robinslange/learning-loop (13 stars, last pushed 4d ago), licensed Apache-2.0. It adds 90 tokens to every session and 2,537 once invoked, about $0.0004 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-08-30.
inbox compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| inboxrobinslange/learning-loop | Skill | 13 | 4d ago | Apache-2.0 | A | 90 | Claude Code |
| Migratedanielmiessler/LifeOS | Skill | 20k | yesterday | MIT | A | 104 | Claude Code, Codex |
| Cortexdanielmiessler/LifeOS | Skill | 20k | yesterday | MIT | A | 184 | Claude Code |
| Profiledanielmiessler/LifeOS | Skill | 20k | yesterday | MIT | A | 108 | Claude Code, Codex |
| wiki-dashboardAr9av/obsidian-wiki | Skill | 3.7k | yesterday | MIT | A | 42 | Claude Code |
| relevance-coarse-filterelvisun/newsjack | Skill | 1.7k | yesterday | MIT | A | 57 | Claude Code |
| session-compactcodeaholicguy/ai-devkit | Skill | 1.7k | 2d ago | Apache-2.0 | A | 39 | Claude Code |