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/remove-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/remove-project)<a href="https://agentmods.dev/commands/thedecipherist/claude-code-mastery-project-starter-kit/remove-project"><img src="https://agentmods.dev/badge/commands/thedecipherist/claude-code-mastery-project-starter-kit/remove-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.00008 | $0.00727 |
| Opus 5 | $0.00004 | $0.00364 |
| Sonnet 5 | $0.00002 | $0.00145 |
| Haiku 4.5 | $0.00001 | $0.00073 |
Grade C, and why
remove-project scanned grade C 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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Delete the directory: `rm -rf <path>` How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remove Project — Unregister and Optionally Delete
Remove a project from the starter kit registry and optionally delete its files from disk.
Arguments: $ARGUMENTS
Steps
1. Read the registry
Read ~/.claude/starter-kit-projects.json. If the file does not exist, tell the user:
No projects have been created yet. Nothing to remove.
And stop.
2. Find the project
Search the registry for a project matching $ARGUMENTS (by name).
If no argument provided:
- List all projects by name
- Ask via AskUserQuestion: "Which project do you want to remove?"
- Options: list all project names from the registry
If the project name is not found:
- Tell the user: "Project
<name>not found in the registry." - Show the list of registered projects
- Stop
3. Show project details
Display the project details:
Project: my-app
Path: ~/projects/my-app
Profile: default
Language: node
Framework: next
Created: 2025-01-15
Status: exists on disk / directory not found
4. Ask what to do
Ask via AskUserQuestion: "What do you want to do with this project?"
- Remove from registry only — Keep the files, just remove the tracking entry
- Delete everything — Delete the project directory AND remove from registry
5a. If "Remove from registry only"
- Read
~/.claude/starter-kit-projects.json - Remove the matching project entry from the
projectsarray - Write the updated registry back
- Confirm: "Removed
<name>from the project registry. Files at<path>are untouched."
5b. If "Delete everything"
Safety check — ask for explicit confirmation:
Ask via AskUserQuestion: "Are you sure you want to permanently delete <path> and all its contents? This cannot be undone."
- Yes, delete it — Proceed with deletion
- No, cancel — Stop without deleting
If confirmed:
- Check if the project directory exists on disk
- If it exists:
- Check for uncommitted git changes:
cd <path> && git status --porcelain 2>/dev/null - If there are uncommitted changes, WARN the user and ask again: "This project has uncommitted changes. Are you SURE you want to delete?"
- Delete the directory:
rm -rf <path>
- Check for uncommitted git changes:
- Remove the entry from
~/.claude/starter-kit-projects.json - Confirm: "Deleted
<path>and removed<name>from the registry."
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 · 96 lines · 8 tokens per session scan C 64889af423e1
remove-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 8 tokens to every session and 727 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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.