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/projects-createdgit 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/projects-created)<a href="https://agentmods.dev/commands/thedecipherist/claude-code-mastery-project-starter-kit/projects-created"><img src="https://agentmods.dev/badge/commands/thedecipherist/claude-code-mastery-project-starter-kit/projects-created.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.00570 |
| Opus 5 | $0.00004 | $0.00285 |
| Sonnet 5 | $0.00002 | $0.00114 |
| Haiku 4.5 | $0.00001 | $0.00057 |
Grade A, and why
projects-created 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 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.
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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Projects Created — Starter Kit Project Registry
List every project that was scaffolded by /new-project, with creation date, profile used, and location.
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. Use
/new-project my-appto scaffold your first project.
And stop.
2. Parse and validate
The registry format is:
{
"projects": [
{
"name": "my-app",
"path": "/home/user/projects/my-app",
"profile": "default",
"language": "node",
"framework": "next",
"database": "mongo",
"createdAt": "2025-01-15T10:30:00Z"
}
]
}
3. Check which projects still exist on disk
For each project in the registry, check if the directory still exists:
ls -d /path/to/project 2>/dev/null
Mark projects whose directory no longer exists as (missing).
4. Display the table
Print a formatted table sorted by creation date (newest first):
=== Projects Created by Starter Kit ===
# Name Profile Language Framework Database Created Path
1 my-app default node next mongo 2025-01-15 ~/projects/my-app
2 my-api python-api python fastapi postgres 2025-01-14 ~/projects/my-api
3 old-project go go gin mongo 2025-01-10 ~/projects/old-project (missing)
Total: 3 projects (2 active, 1 missing)
Tip: Use /remove-project <name> to remove a project and its registry entry.
5. Handle empty registry
If the registry exists but has zero projects:
No projects in the registry. Use
/new-project my-appto scaffold a project.
Notes
- The registry is stored at
~/.claude/starter-kit-projects.json(global — shared across all starter kit instances) - Projects are registered automatically by
/new-projectafter successful scaffolding - Missing projects still appear in the list — use
/remove-projectto clean them up - The registry file is NEVER committed to git (it's in
~/.claude/)
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 · 80 lines · 8 tokens per session scan A d379bfac3325
projects-created 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 570 once invoked, about $0.0000 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-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.