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/install-globalgit 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/install-global)<a href="https://agentmods.dev/commands/thedecipherist/claude-code-mastery-project-starter-kit/install-global"><img src="https://agentmods.dev/badge/commands/thedecipherist/claude-code-mastery-project-starter-kit/install-global.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.00015 | $0.01231 |
| Opus 5 | $0.00008 | $0.00616 |
| Sonnet 5 | $0.00003 | $0.00246 |
| Haiku 4.5 | $0.00002 | $0.00123 |
Grade B, and why
install-global 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.
[ -f ~/.claude/settings.json ] && echo "EXISTING_SETTINGS" || echo "NO_SETTINGS" How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Install Global Config
$ARGUMENTS
Install the starter kit's global Claude configuration into ~/.claude/. This is a one-time setup that gives you security rules, hooks, and settings across ALL projects.
Smart merge: If you already have a global config, this merges new content — it never overwrites your existing rules.
Step 1 — Check What Exists
# Check if global claude directory exists
ls -la ~/.claude/ 2>/dev/null || echo "NO_GLOBAL_DIR"
# Check for existing files
[ -f ~/.claude/CLAUDE.md ] && echo "EXISTING_CLAUDE_MD" || echo "NO_CLAUDE_MD"
[ -f ~/.claude/settings.json ] && echo "EXISTING_SETTINGS" || echo "NO_SETTINGS"
[ -d ~/.claude/hooks ] && echo "EXISTING_HOOKS" || echo "NO_HOOKS"
Step 2 — Handle Each File
2A. ~/.claude/CLAUDE.md
If NO existing file:
- Copy
global-claude-md/CLAUDE.mddirectly to~/.claude/CLAUDE.md - Report: "Installed global CLAUDE.md (fresh install)"
If existing file found:
- Read BOTH files:
- The existing
~/.claude/CLAUDE.md - The starter kit's
global-claude-md/CLAUDE.md
- The existing
- Compare section by section. The starter kit has these sections:
## Identity## NEVER EVER DO## New Project Setup## Coding Standards (All Projects)## Workflow
- For each section:
- If the section header already exists in the user's file → SKIP (don't overwrite their version)
- If the section header does NOT exist → APPEND it to the end of the user's file
- Report exactly what was added and what was skipped:
Global CLAUDE.md merge: ✓ Identity — already exists, skipped ✓ NEVER EVER DO — already exists, skipped + New Project Setup — added + Coding Standards — added ✓ Workflow — already exists, skipped
IMPORTANT: NEVER delete or overwrite existing content. Only append missing sections.
2B. ~/.claude/settings.json
If NO existing file:
- Copy
global-claude-md/settings.jsondirectly to~/.claude/settings.json - Report: "Installed global settings.json (fresh install)"
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 · 146 lines · 15 tokens per session scan B 6923ea1cf132
install-global 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 15 tokens to every session and 1,231 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.