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 mshadmanrahman/claude-for-designers --skill pick-upgit clone --depth 1 https://github.com/mshadmanrahman/claude-for-designersWrote 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/mshadmanrahman/claude-for-designers/pick-up)<a href="https://agentmods.dev/skills/mshadmanrahman/claude-for-designers/pick-up"><img src="https://agentmods.dev/badge/skills/mshadmanrahman/claude-for-designers/pick-up/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/mshadmanrahman/claude-for-designers/pick-up"><img src="https://agentmods.dev/badge/skills/mshadmanrahman/claude-for-designers/pick-up.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.00093 | $0.00673 |
| Opus 5.5 | $0.00037 | $0.00269 |
| Sonnet 5.5 | $0.00019 | $0.00135 |
| Haiku 4.5 | $0.00009 | $0.00067 |
Grade A, and why
pick-up 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 16d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The student typed /pick-up, maybe followed by a project name. This is a fresh chat and it knows nothing about yesterday. Your job is to read their last log entry and tell them where they left off, so they start working in under a minute.
Read only. This skill writes nothing.
Step 1. Find the right log
Logs live at projects/<client>/log.md and career-vault/log.md. Ignore projects/_new-client/, which is a template.
Pick the log in this order, and stop at the first one that applies:
- They named a project (
/pick-up acme). Use that project's log. Match loosely: "acme" findsprojects/acme-fintech/, "career" or "vault" findscareer-vault/log.md. - Claude Code is open inside one project folder. Use that folder's
log.md. - Only one log exists. Use it.
- Several logs exist. Read only the first entry of each and show a menu, most recent first:
You have three projects with a log:
1. acme-fintech yesterday Next: dashboard empty states
2. edubridge 3 days ago Next: write scope-email.md
3. career-vault last week Next: finish 02-portfolio-story.md
Which one?
Then wait for their answer.
If no log exists anywhere, say so in one line and point them to /wrap-up at the end of today's session. Then offer the normal orientation from CLAUDE.md.
Step 2. Read the newest entry only
Read the first entry under the header. Do not read older entries unless they ask. Do not read the whole project folder yet; the entry names the files that matter.
Then open the file the Next line names, if it names one, so you know its current state before you speak. If that file already looks finished, say so: they may have done more after the last wrap-up.
Step 3. Tell them, in this shape
Last time (2 Oct, Class 3) you finished the interrogated brief and
decided bKash is its own flow. Still open: who handles refunds.
Next step: write scope-email.md. Start there, or deal with the
refund question first?
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.
- 16d ago First seen · 54 lines · 93 tokens per session scan A bab30e2177d9
pick-up is a skill published in the GitHub repository mshadmanrahman/claude-for-designers (39 stars, last pushed 16d ago), licensed MIT. It adds 93 tokens to every session and 673 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-09-30.
Other skills, from other repositories
customer-success
Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.
event-planner
Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.
hr-talent
HR and talent management expertise for talent acquisition, performance management, compensation strategy, organizational design, culture building, succession planning, and D&I programs. Use when hiring, managing performance, designing organizations, or building culture.
leadership
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.
operations
Operations excellence expertise for supply chain optimization, process improvement (Lean, Six Sigma), capacity planning, vendor management, quality assurance, and operational efficiency. Use when optimizing processes, managing supply chains, or improving operational performance.
process-flowchart-designer
Create process flowcharts and workflow diagrams from descriptions, with optimization suggestions and bottleneck identification. Use when mapping processes, designing workflows, or improving operational efficiency.