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.
git clone --depth 1 https://github.com/ankushdixit/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/commands/ankushdixit/claude-plugins/start)<a href="https://agentmods.dev/commands/ankushdixit/claude-plugins/start"><img src="https://agentmods.dev/badge/commands/ankushdixit/claude-plugins/start/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/commands/ankushdixit/claude-plugins/start"><img src="https://agentmods.dev/badge/commands/ankushdixit/claude-plugins/start.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.00008 | $0.01056 |
| Opus 5.5 | $0.00003 | $0.00422 |
| Sonnet 5.5 | $0.00002 | $0.00211 |
| Haiku 4.5 | $0.00001 | $0.00106 |
Grade A, and why
start 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Start
Step 1: Determine Work Item to Start
If user provided a work item ID in $ARGUMENTS:
- Skip to Step 3 and start that specific work item
If no work item ID provided:
- Continue to Step 2 for interactive selection
Step 2: Get Recommendations and Ask User
Get the top 4 recommended work items:
python -m solokit.work_items.get_next_recommendations --limit 4
This will output ready-to-start work items in format:
work_item_id | type | title | priority
Parse the output and present options using AskUserQuestion:
Question: Which work item do you want to start?
- Question: "Select a work item to start working on:"
- Header: "Work Item"
- Multi-select: false
- Options (up to 4):
- Label: "{work_item_id}: {title}", Description: "Type: {type} | Priority: {priority}"
- Label: "{work_item_id}: {title}", Description: "Type: {type} | Priority: {priority}"
- Label: "{work_item_id}: {title}", Description: "Type: {type} | Priority: {priority}"
- Label: "{work_item_id}: {title}", Description: "Type: {type} | Priority: {priority}"
Example option formatting:
- Label: "feature_auth: Add user authentication"
- Description: "Type: feature | Priority: high"
If no ready work items found:
- The script will exit with error
- Show message: "No work items ready to start. All items are blocked by dependencies or already in progress."
- Display hint: "Use /work-list to see all work items and their status."
- Exit without calling command
Step 3: Start Session
Based on the selected work item ID (either from user argument or interactive selection):
sk start {work_item_id}
Replace {work_item_id} with:
- The value from
$ARGUMENTSif user provided it - The selected work item ID from Step 2 if interactive selection was used
The briefing includes:
- Complete project context (technology stack, directory tree, documentation)
- Previous work context (for in-progress items) - commits made, files changed, quality gates from prior sessions
- Full work item specification from
.session/specs/{work_item_id}.md(source of truth) - Work item tracking details (title, type, priority, dependencies)
- Spec validation warnings (if specification is incomplete)
- Top 10 relevant learnings scored by keyword matching, type relevance, recency, and category
- Milestone context and progress (if the work item belongs to a milestone)
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 · 127 lines · 8 tokens per session scan A bebc0753c8b4
start is a command published in the GitHub repository ankushdixit/claude-plugins (3 stars, last pushed 9mo ago), licensed MIT. It adds 8 tokens to every session and 1,056 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.