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/thedecipherist/claude-code-mastery-project-starter-kit/update-projectgit clone --depth 1 https://github.com/TheDecipherist/claude-code-mastery-project-starter-kitWrote 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/thedecipherist/claude-code-mastery-project-starter-kit/update-project)<a href="https://agentmods.dev/commands/thedecipherist/claude-code-mastery-project-starter-kit/update-project"><img src="https://agentmods.dev/badge/commands/thedecipherist/claude-code-mastery-project-starter-kit/update-project.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.00016 | $0.03909 |
| Opus 5 | $0.00008 | $0.01954 |
| Sonnet 5 | $0.00003 | $0.00782 |
| Haiku 4.5 | $0.00002 | $0.00391 |
Grade B, and why
update-project 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.
1. Read both `$SOURCE/.claude/settings.json` and `$TARGET/.claude/settings.json` as JSON How it starts
The opening of the file, as written. The whole thing — 414 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Starter Kit Project
Update an existing starter-kit project with the latest commands, hooks, skills, and rules from the current starter kit source. Smart merge — replaces starter kit files with newer versions while preserving any custom files the user created themselves.
Arguments: $ARGUMENTS
Step 0 — Resolve Source (Starter Kit)
Find the starter kit source directory:
- If CWD has BOTH
claude-mastery-project.confAND.claude/commands/new-project.md→ use CWD as$SOURCE - Else read
~/.claude/starter-kit-source-path→ verify it still has both files - Else ask via AskUserQuestion: "Where is the starter kit cloned?" with a text input
Store as $SOURCE.
Step 1 — Registry Picker (Select Target)
-
Read
~/.claude/starter-kit-projects.json- If file doesn't exist or empty → error: "No projects found. Use
/new-projectto create one first." - If file is invalid JSON → error: "Project registry is corrupted. Check
~/.claude/starter-kit-projects.json."
- If file doesn't exist or empty → error: "No projects found. Use
-
Filter to projects whose
pathdirectory still exists on disk -
If no valid projects remain → error: "No registered projects found on disk. Use
/new-projectto create one." -
Display list with AskUserQuestion:
- "Which project do you want to update?"
- Options: up to 4 most recent projects (by
createdAt), each showing:name — language/framework — path - If more than 4: the 4th option should be "Other (type a path)"
-
Store selected path as
$TARGET
Validations (all must pass — stop with clear error if any fail)
$TARGETdirectory exists → if not: "Directory not found: $TARGET"$TARGETis a git repo → run:git -C "$TARGET" rev-parse --is-inside-work-tree 2>/dev/null- If not a git repo: "This project must be a git repo. Run
git init && git commit --allow-empty -m 'init'first."
- If not a git repo: "This project must be a git repo. Run
$TARGETis NOT the starter kit itself (compare resolved paths of$SOURCEand$TARGET)- If same: "Cannot update the starter kit itself."
$TARGETis registered in~/.claude/starter-kit-projects.json- If not registered: "This project isn't in the registry. Use
/convert-project-to-starter-kitinstead."
- If not registered: "This project isn't in the registry. Use
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.
- 4d ago First seen · 414 lines · 16 tokens per session scan B 20ed53fd3c49
update-project 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 16 tokens to every session and 3,909 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.
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.