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/apurvbazari/claude-plugins/adoptnpx skills add ApurvBazari/claude-plugins --skill adoptgit clone --depth 1 https://github.com/ApurvBazari/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/apurvbazari/claude-plugins/adopt)<a href="https://agentmods.dev/skills/apurvbazari/claude-plugins/adopt"><img src="https://agentmods.dev/badge/skills/apurvbazari/claude-plugins/adopt.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.00065 | $0.03604 |
| Opus 5 | $0.00032 | $0.01802 |
| Sonnet 5 | $0.00013 | $0.00721 |
| Haiku 4.5 | $0.00006 | $0.00360 |
Grade A, and why
adopt 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 3d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adopt Skill — Retrofit Foreign Claude Tooling
You are running the onboard adopt skill. It brings a project's pre-existing, hand-crafted Claude tooling under onboard management by synthesizing a baseline — onboard-meta.json (mode:"retrofit") plus snapshots — so /onboard:update can manage it. Adopt never modifies a hand-crafted file. It writes only the baseline; all modernization is deferred to /onboard:update, per-item approved.
This skill may be entered three ways: directly (/onboard:adopt), from /onboard:start's existing-config branch (the Adopt option), or from /onboard:update's missing-meta guard (offer adopt → continue into drift detection). When entered from update, after A6 hand back control to update's drift detection.
Overview
Tell the developer:
Adopting your existing Claude tooling — I'll catalog what you already have, research your codebase to ground the baseline, confirm a few preferences, then show you a full preview before writing anything. I won't touch your hand-crafted files — I only record a baseline so
/onboard:updatecan manage them going forward.
Step 0: Initialize Phase Tracking
Runs first, before Step A1. This wires the durable phase-task list that the rest of the flow transitions for in-session visibility.
First, read the contract: ../start/references/phase-tracking.md (the cross-skill source of truth — start is its worked example). It defines the task subjects, the pending → in_progress → completed (plus deleted) state machine, and the HARD GATE mapping. Follow it verbatim — do not re-derive its rules here. adopt operates on a project that already has hand-crafted tooling and writes its own onboard-meta.json only at the end (Step A6), so the task list here is in-session progress visibility; the durable record lives in the on-disk artifacts the contract describes (the baseline meta + snapshots written at A6).
Create the 6 adopt phase tasks via TaskCreate, all status: "pending", one per ladder phase, using the adopt: subject prefix from the contract's § Other entry points table:
What ships with it
2 files 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.
- 3d ago First seen · 142 lines · 65 tokens per session scan A 99b70038c4c5
adopt is a skill published in the GitHub repository ApurvBazari/claude-plugins (0 stars, last pushed 28d ago), licensed MIT. It adds 65 tokens to every session and 3,604 once invoked, about $0.0003 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
cross-platform
Cross-platform development patterns for macOS, Windows, and Linux.
shell-scripting
Shell scripting best practices for cross-platform CLI tools.
c-notify
Send native macOS notification center alerts from the command line using terminal-notifier.
chat-complex-documents
Chat with and search your complex documents — ask questions, extract tables and fields, and get answers grounded in the source. Connects the hosted Unstructured Transform MCP server to parse, structure, and enrich PDFs, Word/Excel/PowerPoint, images, scanned files, emails, and 60+ other formats into clean, AI-ready…
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.