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 technicalpickles/pickled-claude-plugins/plugin install second-brainWrote 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/technicalpickles/pickled-claude-plugins/process-inbox)<a href="https://agentmods.dev/skills/technicalpickles/pickled-claude-plugins/process-inbox"><img src="https://agentmods.dev/badge/skills/technicalpickles/pickled-claude-plugins/process-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/technicalpickles/pickled-claude-plugins/process-inbox"><img src="https://agentmods.dev/badge/skills/technicalpickles/pickled-claude-plugins/process-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.00029 | $0.01234 |
| Opus 5.5 | $0.00012 | $0.00494 |
| Sonnet 5.5 | $0.00006 | $0.00247 |
| Haiku 4.5 | $0.00003 | $0.00123 |
Grade A, and why
process-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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Process Inbox
Process accumulated inbox notes through the full pipeline: ingest, enrich, route, connect, link to daily note.
See references/pipeline.md for stage definitions and status flow.
Step 1: Load Configuration
npx @techpickles/sb config default
npx @techpickles/sb config vaults
If no vault configured:
Second brain not configured. Run /second-brain:setup first.
Load skill references:
second-brain:obsidianfor tool mechanicsreferences/pipeline.mdfor stage definitionsreferences/routing-memory.mdfor learning loopreferences/routing.mdfor scoring algorithmreferences/connecting.mdfor connection discoveryreferences/daily-linking.mdfor daily note linkingreferences/sb-cli.mdfor sb command reference
Step 2: Survey Inbox
npx @techpickles/sb inbox list --detail
Parse the JSON response. Group notes by status field (notes without status are raw).
Check for stale notes (captured more than 14 days ago based on captured frontmatter field).
Present summary:
Inbox: {total} notes
{n} raw (session notes awaiting ingestion)
{n} ingested (insights awaiting enrichment)
{n} enriched (notes awaiting routing)
{n} pending-review (need your input)
{n} routed (awaiting connection)
{n} connected (awaiting daily linking)
{If stale notes exist:}
Heads up: {n} notes have been in the inbox for over 2 weeks.
If inbox is empty:
Inbox is empty. Nothing to process.
Step 3: Process by Stage
Work through notes in pipeline order. Each stage picks up notes at its expected input status.
3a: Ingest raw session notes
For each note with status: raw and type: session-notes:
- Follow the
ingestskill (keeps the note whole by default, only splits on a real cross-topic signal) - Report:
Ingested: {session filename}(default case), orIngested: {session filename} -> {n} insights (split)(exception case)
3b: Enrich ingested insights
For each note with status: ingested and type: insight:
- Follow the
enrichskill to create proper zettelkasten notes - Report:
Enriched: {filename}
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 First seen · 149 lines · 29 tokens per session scan A 9a278d7b2624
process-inbox is a skill published in the GitHub repository technicalpickles/pickled-claude-plugins (11 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 1,234 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
doc-bootstrapping
A project-documentation setup guide that creates a central set of rules, memory notes, and Diátaxis documentation folders. Diátaxis is a method that separates explanations, specifications, how-to guides, and tutorials.
suggest-automations
Offer the three most common automations for a user as a single-choice card, from your own knowledge of their team and their apps, then build the one they choose once they confirm, or offer more. The system preloads it on onboarding threads, where the opening card already asked the user about themselves. Use it on…
customer-journey-map
Construye un mapa de recorrido del cliente para un producto, servicio o experiencia. Úsalo cuando se te pida mapear un recorrido del cliente, crear un viaje del usuario, documentar puntos de contacto y puntos de fricción, o diseñar un mapa de experiencia. Produce un mapa de recorrido completo con etapas, puntos de…
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…
scenario-zbrush-expert
Use when an agent drives Maxon ZBrush 2026 for any task (sculpt in ZBrush, DynaMesh, ZRemesher, UVs, export, polypaint, posing, 3D print, clean up an AI mesh in ZBrush), when writing ZBrush Python (zbrush.commands) or ZScript, when the ZBrush bridge is not answering, a palette path or set() does nothing, a scripted…
company-brain
Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so an agent can answer on your team's behalf. Team-scope sibling to second-brain. Modes — capture, compile (wiki pages + INDEX.md), query (trust-weighted, saved to outputs/), review (verify / deprecate / supersede…