agentmods.dev

starter-kit

starter-kit is a command for Claude Code from TheDecipherist/claude-code-mastery-project-starter-kit. It costs 25 tokens per session (860 once invoked), scanned B, original, MIT.

A command for managing the globally installed Starter Kit, a collection of commands and skills for Claude Code projects.

In plain words
What is it for?
Use it to update the kit, view its status, or install it in the current project. It requires npm or npx for updates.
Why use it?
It provides one place to update the kit, check its installation, or add it to the current project instead of managing linked files by hand.

Command for Claude Code

not rated 337 +1 2mo ago B scan 25 tokens original MIT
View the source file TheDecipherist/claude-code-mastery-project-starter-kit
Install

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.

agentmods
npx agentmods add commands/thedecipherist/claude-code-mastery-project-starter-kit/starter-kit
Clone the repo
git clone --depth 1 https://github.com/TheDecipherist/claude-code-mastery-project-starter-kit

Made for: Claude Code.

Wrote 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.

agentmods badge for starter-kit

README.md
[![agentmods](https://agentmods.dev/badge/commands/thedecipherist/claude-code-mastery-project-starter-kit/starter-kit.svg)](https://agentmods.dev/commands/thedecipherist/claude-code-mastery-project-starter-kit/starter-kit)
Your own site
<a href="https://agentmods.dev/commands/thedecipherist/claude-code-mastery-project-starter-kit/starter-kit"><img src="https://agentmods.dev/badge/commands/thedecipherist/claude-code-mastery-project-starter-kit/starter-kit.svg" alt="Measured on agentmods" height="20"></a>
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 860 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00025 $0.00860
Opus 5 $0.00013 $0.00430
Sonnet 5 $0.00005 $0.00172
Haiku 4.5 $0.00003 $0.00086

Measured 4d ago against content hash 07ae8230a431, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

starter-kit scanned grade B with 1 finding 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 4d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

cat ~/.claude/starter-kit/version
.claude/commands/starter-kit.md · 91 lines

How it starts

The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/starter-kit

Manage the globally installed @claude-code-mastery/starter-kit.

The kit is installed in ~/.claude/starter-kit/. Commands and skills are symlinked from there into ~/.claude/commands/ and ~/.claude/skills/, so updating the starter-kit directory instantly updates everything without needing to re-symlink.

Detect subcommand

Read the user's argument: $ARGUMENTS

  • update → run Update flow below
  • status → run Status flow below
  • add → run Add flow below
  • empty or unrecognised → show usage

Update flow

Check whether npm is available, then run:

npx @claude-code-mastery/starter-kit update

This overwrites ~/.claude/starter-kit/ with the latest published version, symlinks any new commands or skills that were added, and registers any new hooks in ~/.claude/settings.json.

After the command completes, report the version that is now installed:

cat ~/.claude/starter-kit/version

Tell the user: "✅ Starter kit updated to v. New commands and hooks are active immediately."

If npm / npx is not available, tell the user to install Node.js from https://nodejs.org and then run npx @claude-code-mastery/starter-kit update in their terminal.

Status flow

Check the installed version and compare with the registry:

npx @claude-code-mastery/starter-kit status

Show the output to the user as-is. If the kit is not installed, tell the user to run npx @claude-code-mastery/starter-kit init from any terminal to install it.

Add flow

Install the starter kit into the current project's .claude/ directory. This is the project-level equivalent of the global install — it gives the project its own copy of commands, hooks, and skills that Claude Code picks up automatically.

Steps:

  1. Check whether ~/.claude/starter-kit/ exists. If not, tell the user to run the global install first: npx @claude-code-mastery/starter-kit init
  2. Check whether .claude/ already exists in the current project:
    • If it does, ask the user: ".claude/ already exists in this project. Merge the starter-kit files in? Existing files with matching names will NOT be overwritten." (yes / no)
    • If no: stop.
  3. Copy from ~/.claude/starter-kit/ into .claude/: 
    cp -rn ~/.claude/starter-kit/commands/ .claude/commands/
cp -rn ~/.claude/starter-kit/hooks/ .claude/hooks/
cp -rn ~/.claude/starter-kit/skills/ .claude/skills/
    (-n = no-clobber: never overwrites existing files)
  4. If .claude/settings.json does not exist in the project, copy from the starter-kit: 
    cp ~/.claude/starter-kit/settings.json .claude/settings.json
    If it does exist, remind the user to manually merge the hook entries from ~/.claude/starter-kit/settings.json if needed.
  5. Report: "✅ Starter kit added to this project's .claude/ directory. Commands and hooks are active for this project."

Read the full file on GitHub · 91 lines

Changes

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.

  1. 4d ago First seen · 91 lines · 25 tokens per session scan B 07ae8230a431

Subscribe to this mod's changes

starter-kit is a command published in the GitHub repository TheDecipherist/claude-code-mastery-project-starter-kit (337 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 860 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other commands, from other repositories

git

Git operations with intelligent commit messages and workflow optimization.

SuperClaude-Org/SuperClaude_Framework · 11 tokens

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

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.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

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.

github/spec-kit · 35 tokens