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 jhlee0409/omni-harness-kit --skill pickupgit clone --depth 1 https://github.com/jhlee0409/omni-harness-kitWrote 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/jhlee0409/omni-harness-kit/pickup)<a href="https://agentmods.dev/skills/jhlee0409/omni-harness-kit/pickup"><img src="https://agentmods.dev/badge/skills/jhlee0409/omni-harness-kit/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/jhlee0409/omni-harness-kit/pickup"><img src="https://agentmods.dev/badge/skills/jhlee0409/omni-harness-kit/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.00075 | $0.00385 |
| Opus 5 | $0.00037 | $0.00192 |
| Sonnet 5 | $0.00015 | $0.00077 |
| Haiku 4.5 | $0.00007 | $0.00038 |
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 9d 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.
What it actually says
pickup
Re-establish where the work left off — from the resume block ALONE, without asking the user to re-narrate.
- Find the resume block. Prefer an active spec's
specs/*/context.md## 0. Resume hereblock (use the[spec-slug]arg to disambiguate when several exist) — that is where/harness-kit:handoffwrites when a spec is active; fall back to.claude/handoff.md. When both exist, use the most recently modified — it is the freshest handoff. If none is found, say so plainly — don't guess. - Read it fully, then re-ground in the repo:
git status --short,git log --oneline -5, and read the files it lists. Confirm the stated state matches reality (files actually changed, the next command still makes sense). - Restate the original ask + where you are (phase / N of M) + the single next action — then DO that next action. Do NOT redo the "Don't redo" items.
- If the block contradicts the repo (says a file was changed but it wasn't), surface the conflict instead of trusting the block blindly.
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.
- 9d ago First seen · 29 lines · 75 tokens per session scan A 655f689d8447
pickup is a skill published in the GitHub repository jhlee0409/omni-harness-kit (2 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session and 385 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
alive:system-cleanup
The world feels messy. Stale tasks, orphan folders, v2 remnants, unsaved sessions — entropy is accumulating and needs to be addressed before it compounds. Scans across all walnuts, then surfaces issues one at a time.
alive:world
The human doesn't know what to work on, or wants to see everything at once. They need the big picture — what's active, what's stale, what needs attention. Renders a live world view grouped by ALIVE domain, then routes to open, tidy, find, history, or map.
alive:settings
The human wants to adjust how the system behaves — not what it contains, but how it feels. Voice, rhythm, preferences, walnut-level config, full permissions toggleable, named squirrel config, action logging toggle. The system adapting to them. Routes to preferences.yaml or walnut config.yaml depending on scope. For…
tokenhabit
A coaching tool that finds habits in past coding-agent conversations that waste tokens, the text units used to process requests and responses, and suggests ways to reduce that waste.
ccc-spawn
Click-first spawn hub — spin isolated work into its own session on demand: a spawntask chip in Cowork, a /spawn peer in the CLI. Also routes to $ccc-fleet or $ccc-relay.
stacks
Load stack-specific knowledge (conventions, exact lint/test/build commands, common failure patterns) onto the current role agent for the project's detected tech stack(s) — Next.js, React Native, Spring Boot, FastAPI, Django, Rust, etc. Use at the start of any task in an unfamiliar or newly-onboarded repo, or whenever…