Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add davistroy/claude-marketplace/plugin install personal-pluginWrote 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/davistroy/claude-marketplace/clear-prep)<a href="https://agentmods.dev/skills/davistroy/claude-marketplace/clear-prep"><img src="https://agentmods.dev/badge/skills/davistroy/claude-marketplace/clear-prep/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/davistroy/claude-marketplace/clear-prep"><img src="https://agentmods.dev/badge/skills/davistroy/claude-marketplace/clear-prep.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.00114 | $0.02134 |
| Opus 5.5 | $0.00046 | $0.00854 |
| Sonnet 5.5 | $0.00023 | $0.00427 |
| Haiku 4.5 | $0.00011 | $0.00213 |
Grade A, and why
clear-prep 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 1mo 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clear Prep
Prepare the project to survive a context reset. When you are about to run /clear (or a compaction is imminent), the volatile session state — what you just did, what is half-done, what the next step is — lives only in conversation context and is lost the moment context clears. This skill persists that state into the project's durable documents, then hands you a ready-to-paste resume prompt so the next session continues seamlessly.
Two guarantees:
- Nothing in-flight is lost — every persistent document that should reflect the current state is updated before you clear.
- The next session starts oriented — the resume prompt tells a zero-context Claude exactly what to read, where things stand, and what to do next.
This skill writes only to documentation/state files (all git-recoverable). It does NOT commit, push, or clear context — you do that.
Input
Arguments: $ARGUMENTS
Optional:
- A short note on the intended next task (e.g.,
finish the CVE remediation PR) — sharpens the "next task" line in the resume prompt. --no-write— skip document updates; only generate the resume prompt from current state (dry-run / read-only).
Dynamic context available:
!`git status -s 2>/dev/null || echo "(not a git repository)"`— uncommitted changes!`git log --oneline -8 2>/dev/null || echo "(not a git repository)"`— recent commits!`git branch --show-current 2>/dev/null || echo "(not a git repository)"`— active branch
Instructions
Execute the phases in order. Phase 2 is skipped when --no-write is passed.
Phase 1: Assess Session State
Reconstruct what this session actually changed and what remains open. Gather:
- Git delta — run
git status -s,git branch --show-current, andgit log --oneline -8. Identify: uncommitted/untracked files, current branch, whether work has been committed or is still loose in the working tree. - What was done this session — from the conversation, summarize the concrete work: decisions made, files created/edited, problems solved, experiments run. Be specific (files, versions, PR numbers), not vague.
- What is in-flight — anything half-finished: a partially written function, an unmerged PR, a plan phase mid-execution, an unanswered question, a failing test.
- The single next action — the one most important thing the next session should do first. Prefer the argument note if the user gave one.
- Orientation surface — detect which durable documents this project uses so the resume prompt can point at them:
LAB_NOTEBOOK.md(Decision Log, Open Action Items, most recent entry, Current Baseline)memory/MEMORY.mdand its topic files (locate the memory dir; on this repo it is<repo>/memory/or the per-project~/.claude/projects/.../memory/)CLAUDE.md,IMPLEMENTATION_PLAN.md,CHANGELOG.md,README.md,BRIEF.md,docs/
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.
- 1mo ago First seen · 137 lines · 114 tokens per session scan A d69ced470196
clear-prep is a skill published in the GitHub repository davistroy/claude-marketplace (5 stars, last pushed 18d ago), licensed MIT. It adds 114 tokens to every session and 2,134 once invoked, about $0.0005 per session on Opus 5.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-09-04.
Other skills, from other repositories
Migrate
Intakes external content (notes, CLAUDE.md, Cursor rules, Obsidian/Notion/Apple Notes exports), classifies chunks against the LifeOS taxonomy, and commits with provenance after confidence-tiered approval. USE WHEN /migrate, migrate content, import from other LifeOS, bring in old notes, import Cursor rules, import…
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
Profile
View, edit, or clear the LifeOS User Model (PRINCIPALIDENTITY.md) — persistent identity context loaded at session startup. Three intents: View, Edit (identity, goals, constraints, preferences), Clear (reset). Read by Algorithm OBSERVE and skills for personalization. USE WHEN profile, show profile, view profile, who am…
wiki-dashboard
Create dynamic, queryable Obsidian dashboard views using Bases or Dataview. Use for auto-updating tables, indexes, or structured views of vault content; not for ordinary question answering.
relevance-coarse-filter
Cheap, high-recall first-pass filter that removes obvious junk from a detector candidate pool before expensive story-origin research and PR judgment. Decides keep, monitoronly, or reject — never ranks, writes angles, verifies dates, or decides whether to pitch.
session-compact
AI DevKit · Compact a historical AI coding session with Jev when context is long, work is handed off or resumed, or durable continuation facts and memory candidates need extraction.