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 skills/technicalpickles/pickled-claude-plugins/devlognpx skills add technicalpickles/pickled-claude-plugins --skill devloggit clone --depth 1 https://github.com/technicalpickles/pickled-claude-pluginsWhat 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.00106 | $0.02248 |
| Opus 5 | $0.00053 | $0.01124 |
| Sonnet 5 | $0.00021 | $0.00450 |
| Haiku 4.5 | $0.00011 | $0.00225 |
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 2d 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 — 202 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
- Project-specific context (a config value, a repo convention) — that belongs in Claude Code's own memory system, 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.
- 2d 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 (10 stars, last pushed 4d ago), licensed MIT. It adds 106 tokens to every session and 2,248 once invoked, about $0.0005 per session on Opus 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
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
verify-security
安全校验关卡。自动扫描代码安全漏洞，检测危险模式，确保安全决策有文档记录。当用户提到安全扫描、漏洞检测、安全审计、代码安全、OWASP、注入检测、敏感信息泄露时使用。在新建模块、安全相关变更、攻防任务、重构完成时自动触发。.
development
开发语言能力索引。Python、Go、Rust、TypeScript、Java、C++、Shell。当用户提到编程、开发、代码、语言时路由到此。.
post-build-flow
Handles workflow verification and setup after build-workflow succeeds, or when the message contains workflow-verification-follow-up or workflow-setup-required. Load after direct builds, when verificationReadiness requires action, or on orchestrator verify/setup follow-up turns.
n8n:create-pr
Creates GitHub pull requests with properly formatted titles that pass the check-pr-title CI validation. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request.
n8n:reproduce-bug
Reproduce a bug from a Linear ticket with a failing test. Expects the full ticket context (title, description, comments) to be provided as input.