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 commands/ankushdixit/claude-plugins/adoptgit clone --depth 1 https://github.com/ankushdixit/claude-pluginsWhat 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.01114 |
| Opus 5 | $0.00005 | $0.00557 |
| Sonnet 5 | $0.00002 | $0.00223 |
| Haiku 4.5 | $0.00001 | $0.00111 |
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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adopt Solokit into Existing Project
Add Solokit session management to an existing project without modifying your code.
When to Use This Command
Use /adopt when you have an existing project with code and want to add:
- Session tracking and briefings
- Work item management
- Learning capture system
- Quality gates
- Claude Code slash commands
Note: For new/blank projects, use /init instead.
Interactive Configuration (3 Questions)
Use the AskUserQuestion tool to collect configuration:
Question 1: Confirm Adoption
Question: "This will add Solokit session management to your existing project. Existing configs may be overwritten. Continue?" Header: "Confirm" Multi-Select: false
Options:
-
Label: "Yes, adopt Solokit" Description: "Add session management, quality gates, and slash commands to this project"
-
Label: "No, cancel" Description: "Exit without making changes"
If the user selects "No, cancel", stop and inform them that adoption was cancelled.
Question 2: Quality Gates Tier
Question: "What level of quality gates do you want?" Header: "Quality Tier" Multi-Select: false
Options:
-
Label: "Essential" Description: "Linting, formatting, type-check, basic tests (fastest setup)"
-
Label: "Standard" Description: "+ Git hooks, security scanning (recommended for most projects)"
-
Label: "Comprehensive" Description: "+ Coverage reports, integration tests, mutation testing (production-ready)"
-
Label: "Production-Ready" Description: "+ Performance monitoring, error tracking, deployment safety (enterprise-grade)"
Question 3: Testing Coverage Target
Question: "What testing coverage level do you want to enforce?" Header: "Coverage" Multi-Select: false
Options:
-
Label: "Basic (60%)" Description: "Minimal coverage for prototypes and MVPs"
-
Label: "Standard (80%)" Description: "Industry standard for production code (recommended)"
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 · 174 lines · 10 tokens per session scan A fe01c35f0e07
adopt is a command published in the GitHub repository ankushdixit/claude-plugins (3 stars, last pushed 7mo ago), licensed MIT. It adds 10 tokens to every session and 1,114 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.