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 skills add 0xmariowu/builders-dont-cry --skill pickupgit clone --depth 1 https://github.com/0xmariowu/builders-dont-cryWrote 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/0xmariowu/builders-dont-cry/pickup)<a href="https://agentmods.dev/skills/0xmariowu/builders-dont-cry/pickup"><img src="https://agentmods.dev/badge/skills/0xmariowu/builders-dont-cry/pickup/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/0xmariowu/builders-dont-cry/pickup"><img src="https://agentmods.dev/badge/skills/0xmariowu/builders-dont-cry/pickup.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.00104 | $0.03081 |
| Opus 5 | $0.00052 | $0.01541 |
| Sonnet 5 | $0.00021 | $0.00616 |
| Haiku 4.5 | $0.00010 | $0.00308 |
Grade A, and why
pickup 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 10d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pickup — Session resume skill
How the candidate table reaches the user (three layers, only one talks to AI)
Claude Code v2.1+ does not print SessionStart hook stdout to the user's terminal — hook output is injected only as a system-reminder into the AI's conversation context. The /pickup design splits "human visibility" from "AI context loading" so neither bloats the other:
-
Shell wrapper (
cc()function in~/.zshrc) — runssession-resume-prompt.sh --listsynchronously before launchingclaude. The boxed table prints in the user's terminal so builder sees the candidates immediately at session start. This is the human-visible layer; AI never sees it. -
SessionStart hook (registered in the host's
.claude/settings.jsonfor Claude Code, with CLI fallback elsewhere) — runs the same script with no args, which emits exactly one line into the AI's context:💡 N active handoff(s). Latest: <topic> (<project>, <when>). Type /pickup to see the list, or /pickup N to load row N.No mapping, no row paths, no [FOR AI] instructions. This is the lightweight awareness layer — AI knows handoffs exist but does not stand by waiting for a digit input. -
/pickupskill (this file) — the only path that loads candidate paths into AI context. Triggered by builder typing/pickup(with optional argument). The skill itself runssession-resume-prompt.sh --mappingto fetch the row → path mapping, then resolves builder's input (digit / keyword) and Reads the chosen handoff file. Mapping enters context only when builder has explicitly asked to pick up.
Mandatory AI behavior when the SessionStart hint is in context:
- If builder types
/pickup(or/pickup 5,/pickup <keyword>) → invoke this skill. The skill internally fetches the mapping; do not ask builder for paths or row counts. - If builder types anything else → proceed with that request normally. Do not assume bare numbers or keywords are pickup commands. Do not nag builder about the pending handoffs.
- If no hint is present (empty handoff dir or hook errored), there is nothing to mention.
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.
- 10d ago First seen · 147 lines · 104 tokens per session scan A e6d5dfc8afb9
pickup is a skill published in the GitHub repository 0xmariowu/builders-dont-cry (4 stars, last pushed 4mo ago), licensed MIT. It adds 104 tokens to every session and 3,081 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
shellm
Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.