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/devlog)<a href="https://agentmods.dev/skills/technicalpickles/pickled-claude-plugins/devlog"><img src="https://agentmods.dev/badge/skills/technicalpickles/pickled-claude-plugins/devlog/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/devlog"><img src="https://agentmods.dev/badge/skills/technicalpickles/pickled-claude-plugins/devlog.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.00106 | $0.02748 |
| Opus 5.5 | $0.00042 | $0.01099 |
| Sonnet 5.5 | $0.00021 | $0.00550 |
| Haiku 4.5 | $0.00011 | $0.00275 |
Grade A, and why
devlog 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 yesterday.
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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Devlog
Overview
Devlog is continuous, point-in-time work commentary: what happened, why, and anything surprising, captured as it happens instead of reconstructed from memory at the end of a session. One narrative session note accumulates every entry from the current session — no separate "learnings" system, no til/cursed split, everything worth remembering goes in the same place.
Processing (routing, connecting, daily-linking) happens later via
/second-brain:process-inbox. This skill only ever appends to the inbox.
Write the entry now, in the same turn as whatever triggered it. Don't
ask "should I log this?" and don't offer to — just write it. Asking is
exactly the failure mode that made the old distill-conversation flow get
skipped: by the time a session ends, you're mentally done, and a skip-able
step gets skipped.
When to write
- Finished a feature or fixed a notable bug
- Wrapping up a work session
- Discovered something non-obvious: a gotcha, undocumented behavior, a workaround that took several tries, a constraint you only noticed after hitting it
When not to write
- Routing, connecting, or moving existing notes — that's
/second-brain:process-inbox - Reading an external source and writing it up — that's
second-brain:capture - Trivially obvious or one-off details you'd never reach for again
- A bare project-specific fact (a config value, a repo convention) with no story behind it — that belongs in Claude Code's own memory system alone, not the vault
Step 1: Load Configuration
Don't preflight-check sb availability — just run it:
npx @techpickles/sb config default && npx @techpickles/sb config vaults
If this fails, run ${CLAUDE_PLUGIN_ROOT}/scripts/diagnose-sb.sh and follow
its guidance rather than re-deriving the checks by hand.
If no default vault is configured:
Second brain not configured. Run /second-brain:setup first.
Step 2: Find or create this session's devlog note
Every entry from the current session lands in ONE note. Never create a second devlog note for a session that already has one.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday Changed · +1 lines a47ff1881ad3
- 11d ago Changed · +44 lines 3c7691cb263a
- 1mo ago First seen · 202 lines · 106 tokens per session scan A ecd99b6458c9
devlog is a skill published in the GitHub repository technicalpickles/pickled-claude-plugins (11 stars, last pushed today), licensed MIT. It adds 106 tokens to every session and 2,748 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-31.
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…