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 anthonysuherli/br8n --skill pickupgit clone --depth 1 https://github.com/anthonysuherli/br8nWrote 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/anthonysuherli/br8n/pickup)<a href="https://agentmods.dev/skills/anthonysuherli/br8n/pickup"><img src="https://agentmods.dev/badge/skills/anthonysuherli/br8n/pickup.svg" alt="Measured on agentmods" 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.00074 | $0.00964 |
| Opus 5 | $0.00037 | $0.00482 |
| Sonnet 5 | $0.00015 | $0.00193 |
| Haiku 4.5 | $0.00007 | $0.00096 |
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 7d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
br8n — Pickup
Pick up where you left off. Two modes from one verb:
- here — replay the 30-second resume card for the current repo+branch (the default fast path; context recovery in seconds rather than by hand).
- selector — list every repo+branch you've captured to, most-recent first, and resume any one of them. The cross-repo way back in.
Step 0 — Branch on the argument
Resolve project = git repo basename, kb = git branch (see
../_shared/preamble-first.md).
- Bare
/br8n:pickupinside a git repo → here mode (Step 1). /br8n:pickup listor/br8n:pickup pick, or not in a git repo → selector mode (Step 2)./br8n:pickup <name>→ callmcp__plugin_br8n_br8n__br8n_projects(), substring-match<name>against project/kb. One match → resume it (Step 1 with that target). Multiple → show the filtered selector (Step 2).
Step 1 — Here mode (resume card)
Call mcp__plugin_br8n_br8n__br8n_resume(project, kb, query) with query =
whatever the user is reorienting toward (omit for the synopsis-only spine).
Lead with the next_action returned by br8n_resume — the card must open
with a single concrete step, not a menu:
Do this now:
<next_action>You were:<latest hypothesis>
If next_action is null (legacy captures), derive a ~two-minute step yourself
from the hypothesis + git_diff_stat (e.g. "open <cursor_file>:<line> and
re-read the failing branch") and lead with that instead. Never open with a list
of options — one pre-selected action first, supporting context after.
Then the supporting context, tersely:
- Branch / files —
cursor_file:cursor_line, open files from the snapshot. - In flight —
git_diff_stat, terminal tail if present. - Synopsis — the
<N>standing topics, titles only.
Route on coverage:
- rich / sparse → you have a card; lead with the next_action (see Step 1).
- gap → no captured context for this branch. Don't dead-end — fall through to
selector mode so the user can pick a repo+branch they have captured (or, if the
selector is also empty, offer
/br8n:captureto start tracking or/br8n:explore <topic>to seed from the web).
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.
- 7d ago First seen · 75 lines · 74 tokens per session scan A 398be354e6b6
pickup is a skill published in the GitHub repository anthonysuherli/br8n (1 stars, last pushed 1mo ago), licensed MIT. It adds 74 tokens to every session and 964 once invoked, about $0.0004 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
repo-guidance
Navigate the Composio SDK monorepo, branch and PR workflow, repo layout, generated-file boundaries, changesets, and shared maintenance rules. Use when work spans multiple packages, when deciding where code belongs, when preparing a PR, or when the user asks about repository conventions rather than a specific SDK…
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.
contributor
End-to-end open source contribution workflow: from scanning issues to submitting PRs. Use this skill whenever the user wants to contribute to an open source project, find issues to fix, submit a pull request, fork a repo to contribute, fix a GitHub issue, or mentions 'open source contribution'. Also trigger when they…
review-gate
Use before an agent-produced diff is committed, pushed, opened as a PR, merged, landed, or applied to user files when explicit implementation approval is missing. Trigger for review gate, review pack, approve before landing, diff first then land, human approval, merge gate, commit gate, push gate, or PR readiness.…
dev-architecture-playbook
Route full software-development architecture work from product intent through design, implementation, testing, release, and operations. Use when the user asks for a complete development architecture, wants to know which Spellbook skills to combine, needs an execution path across…
git-commit-smart
Generates meaningful, conventional commit messages automatically. Use when committing code changes. Analyzes diff to create descriptive commits following best practices.