pickup

A startup command that restores project context before coding work begins. It reads key project instructions and documentation, checks the repository and ongoing work, and outlines the next actions.

In plain words
What is it for?
Use it at the beginning of a task to inspect project guidance, Git status, CI or pull-request status, background processes, and the first checks to run.
Why use it?
It prevents an agent from starting without knowing the project's rules, current branch, pending changes, running tasks, or recent test results.

Command for Codex

Install

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.

agentmods
npx agentmods add commands/raulvidis/openclaw-multi-agent-kit/pickup
Clone the repo
git clone --depth 1 https://github.com/raulvidis/openclaw-multi-agent-kit

Made for: Codex.

Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 104 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00007 $0.00104
Opus 5 $0.00003 $0.00052
Sonnet 5 $0.00001 $0.00021
Haiku 4.5 $0.00001 $0.00010

Measured yesterday against content hash 108279b26f9d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

.agents/commands/pickup.md · 12 lines

What it actually says

Read AGENTS.md and docs/index.md. Then:

  1. Check repo state: !git status -sb, current branch, unpushed commits
  2. Check CI/PR status
  3. List running background processes / sessions
  4. Note what tests last ran and what to run first
  5. Plan next 2-3 actions as bullets, then execute Task: $ARGUMENTS
Changes

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.

  1. yesterday First seen · 12 lines · 7 tokens per session scan A 108279b26f9d

Subscribe to this mod's changes

pickup is a command published in the GitHub repository raulvidis/openclaw-multi-agent-kit (395 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 104 once invoked, about $0.0000 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-30.