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 skills/technicalpickles/pickled-claude-plugins/parknpx skills add technicalpickles/pickled-claude-plugins --skill parkgit clone --depth 1 https://github.com/technicalpickles/pickled-claude-pluginsWrote 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/technicalpickles/pickled-claude-plugins/park)<a href="https://agentmods.dev/skills/technicalpickles/pickled-claude-plugins/park"><img src="https://agentmods.dev/badge/skills/technicalpickles/pickled-claude-plugins/park.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 | $0.00010 | $0.01352 |
| Opus 5 | $0.00005 | $0.00676 |
| Sonnet 5 | $0.00002 | $0.00270 |
| Haiku 4.5 | $0.00001 | $0.00135 |
Grade A, and why
park 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 today.
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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Park
Save the current work session. Park has two modes. Pick one, write that shape, do not mix.
Modes
| Mode | Use when | Heading | Filename |
|---|---|---|---|
| Continuation | Bouncing to a new session, work continues | Parked: |
[topic-slug].md |
| Close-out | Work is done, capturing a record before walking away | Wrapped: |
[topic-slug]-wrapped.md |
Mode Detection
Pick one mode by checking three signals in order. Stop at the first one that resolves.
- Explicit user hint.
- "park, I'm done" / "wrap this up" / "park to close it out" / "park as record" → close-out
- "park, switching sessions" / "park to continue" / "park, picking back up later" → continuation
- Terminal-state inference. If all major next steps are done, no blockers remain, and the current state reads as terminal → close-out. If concrete unfinished next actions exist → continuation.
- Ambiguity fallback. Use the AskUserQuestion tool with one A/B question:
- Question: "Is this a close-out (work is done, archiving) or a continuation (planning to pick this up in a new session)?"
- Options: "Close-out (record)" / "Continuation (handoff)"
Pick once and commit. Do not switch modes mid-write.
Before Writing
- Resolve session ID:
- Preferred: Look for a
Session ID:line in the PostToolUse hook context that this plugin injects whenagent-meta:parkis invoked. Use that value. ATranscript:line may also be present. - Fallback: Run scripts/get-session-id.sh via Bash. If empty, use
unknown.
- Preferred: Look for a
- Gather git branch, worktree path, files touched.
- Resolve output location, in order:
- Project
CLAUDE.md→## Handoffsor## Parking→Location: - User
~/.claude/CLAUDE.md→ same lookup - Default:
.parkinglot/in project root (verify it is gitignored)
- Project
- Check the injected context for a
Park destination:line. This is separate from the CLAUDE.md location above and always optional — it names a command to also send the file to once it's written, e.g. filing it into a second brain vault. Not present unless the user configuredAGENT_PARK_DESTINATIONorAGENT_PARK_DESTINATION_HELPER. Note the template if present; it's used in "After Parking" below.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed · +13 lines d3f021963cb8
- 3d ago First seen · 133 lines · 10 tokens per session scan A 940d93dbfd10
park is a skill published in the GitHub repository technicalpickles/pickled-claude-plugins (10 stars, last pushed yesterday), licensed MIT. It adds 10 tokens to every session and 1,352 once invoked, about $0.0001 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
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
development
开发语言能力索引。Python、Go、Rust、TypeScript、Java、C++、Shell。当用户提到编程、开发、代码、语言时路由到此。.
migrate-skills-between-libraries
Use when moving skills between library workspaces or upgrading from a personal library to a team library. Export from one workspace, import into another.
browse-and-evaluate
Use when exploring the ai-agent-skills catalog to find, compare, and evaluate skills before installing. Always use --fields to limit output size and --dry-run before committing to an install.
build-workspace-docs
Use when regenerating README.md and WORKAREAS.md in a managed library workspace. Always dry-run first to preview changes.
Paper Writing Workflow
Workflow phases for paper-writing tasks: triage, material inventory, research question, literature review, paper outline, data analysis summary, figure storyline, reader testing, and finalize packet. Each phase is a short contract — read the relevant rows for the current task only.