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 commands/zyrexnn/cybermes/pickupgit clone --depth 1 https://github.com/Zyrexnn/CybermesWhat 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.00000 | $0.00220 |
| Opus 5 | $0.00000 | $0.00110 |
| Sonnet 5 | $0.00000 | $0.00044 |
| Haiku 4.5 | $0.00000 | $0.00022 |
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.
This is a copy
100% identical to pickup — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
name: pickup description: Pick up a previous hunt on a target — shows hunt history and untested surface from the autopilot ledger. Usage: /pickup target.com
/pickup
Pick up where you left off on a target.
Renamed from
/resume—/resumeis a reserved Claude Code command.
What This Does
- Reads the target rollup from
~/.claude/bughunter/memory/targets/<host>.json. - Shows hunt history (sessions, last seen, tech stack).
- Lists confirmed findings and the endpoints already tested.
Usage
/pickup target.com
Implementation
The agent reads the rollup directly:
python3 -c "import sys; sys.path.insert(0,'engine'); import memory, json; print(json.dumps(memory.rollup('target.com'), indent=2))"
If No Previous Hunt
No ledger data for target.com. Run /recon then /autopilot target.com 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.
- yesterday First seen · 37 lines · 0 tokens per session scan A 6ea48e72e7ad
pickup is a command published in the GitHub repository Zyrexnn/Cybermes (668 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 220 tokens. A static security scan graded it A with 0 findings. It is 100% identical to pickup, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
aod.deliver
Close a completed feature with automatic documentation updates and cleanup (Triad-enhanced).
aod.project-plan
Create implementation plan with dual sign-off (PM + Architect) - Streamlined v2.
tachi.architecture
Generate an architecture description for tachi threat modeling input.
aod.update
Apply upstream template updates to this adopter project.
aod.roadmap
Scaffold a quarterly roadmap document from completed PRDs with PM sign-off.
aod.score
Re-score an existing idea's ICE rating when circumstances change.