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/technicalpickles/pickled-claude-pluginsWrote 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/commands/technicalpickles/pickled-claude-plugins/process-daily)<a href="https://agentmods.dev/commands/technicalpickles/pickled-claude-plugins/process-daily"><img src="https://agentmods.dev/badge/commands/technicalpickles/pickled-claude-plugins/process-daily/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/commands/technicalpickles/pickled-claude-plugins/process-daily"><img src="https://agentmods.dev/badge/commands/technicalpickles/pickled-claude-plugins/process-daily.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.00008 | $0.00974 |
| Opus 5.5 | $0.00003 | $0.00390 |
| Sonnet 5.5 | $0.00002 | $0.00195 |
| Haiku 4.5 | $0.00001 | $0.00097 |
Grade A, and why
process-daily 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Process Daily Note
Clean up voice transcriptions in a daily note. Works in phases with confirmation between each.
Prerequisite: Vault Context Check
This command only works inside a vault.
Check if current directory is a vault:
ls -d .obsidian 2>/dev/null
If .obsidian/ not found in current directory or parents:
⚠ /second-brain:process-daily only works inside a vault.
You're currently in: {cwd}
Options:
1. Open your vault via symlink: ~/.claude/vaults/{name}
2. Use /second-brain:insight to capture from here
3. devlog captures notable moments automatically — nothing to invoke
Stop execution - do not continue.
Overview (when in vault)
- Load context (daily note, glossary, vault conventions)
- Identify & confirm transcription corrections (batched by category)
- Clean prose (preview before applying)
- Restructure to daily note template (preview before applying)
- Suggest extractions (optional)
Phase 1: Load Context
Step 1.1: Read Vault CLAUDE.md
Read CLAUDE.md at vault root for:
- Daily note location
- Template reference
- Structure conventions
Step 1.2: Find the Daily Note
Get the daily note path using sb:
npx @techpickles/sb daily path
If argument provided: Pass the date to sb:
npx @techpickles/sb daily path --date "{YYYY-MM-DD}"
sb returns the full path to the daily note based on .obsidian config.
If file doesn't exist, inform user and stop.
Step 1.3: Load Glossary
Read Glossary.md if it exists at vault root.
Parse correction mappings by category.
Step 1.4: Assess Content
Read daily note. Report:
Loaded: Fleeting/2026-01-21.md
Glossary: Found ({N} known corrections)
Content: ~{N} words, {structured|unstructured}
Ready to process. Continue? [Yes] [Cancel]
Phase 2: Identify & Confirm Corrections
Present corrections in batches by category:
### Tools & Software (Batch 1 of 4)
| # | Found | → Correction | Context |
|---|-------|--------------|---------|
| 1 | me's | mise | "started using me's" |
| 2 | Claude MT | CLAUDE.md | "added Claude MT" |
✓ Accept all | Enter numbers to reject | ? for more context
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 · 154 lines · 8 tokens per session scan A 36d4babcd606
process-daily is a command published in the GitHub repository technicalpickles/pickled-claude-plugins (11 stars, last pushed yesterday), licensed MIT. It adds 8 tokens to every session and 974 once invoked, about $0.0000 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-31.
Other commands, from other repositories
context
A project-context command that manages a .context directory containing decision notes, session logs, and history. It helps keep a record of why changes were made across Git branches and commits.
setup-context
Set up your Skill Memory — a pm-context.md every skill reads so outputs come back tailored to you.
brain
Set up or use your Professional Brain — init, ingest, recall, or review.
memory-compact
Run a dry run first.
checkpoint
Full memory flush — refresh state.md, append to activity log, route any new decisions/insights, then commit and push.
dossier
Force load of Dossier vault profile (and inbox check) before processing the rest of the user's request.