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/thebeardedbearsas/claude-craft/getting-startedgit clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craftWrote 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/thebeardedbearsas/claude-craft/getting-started)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/getting-started"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/getting-started.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.00011 | $0.02587 |
| Opus 5 | $0.00005 | $0.01293 |
| Sonnet 5 | $0.00002 | $0.00517 |
| Haiku 4.5 | $0.00001 | $0.00259 |
Grade A, and why
getting-started 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 5d 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 — 349 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/getting-started - Your First 10 Minutes with Claude Craft
Welcome! This wizard helps you discover Claude Craft's value in under 10 minutes.
125 commands can feel overwhelming — let's find the 3 that matter most for YOUR project right now.
Step 1: Detect Your Project Stack (30 seconds)
Scanning your project to identify the technology stack...
Actions:
-
Check for technology markers in root directory:
package.json→ JavaScript/TypeScript (React, Angular, Vue.js, React Native, Paperclip)composer.json→ PHP (Symfony, Laravel)pyproject.tomlorrequirements.txt→ Pythonpubspec.yaml→ Flutter/Dart*.csprojor*.sln→ C# / .NETgo.mod→ Gomix.exs→ Elixir
-
For JavaScript/TypeScript projects, check dependencies to determine framework:
- Look for
react,@angular/core,vue,react-nativein package.json dependencies - Look for
@paperclipaior apaperclip.configkey in package.json to detect a Paperclip project (Node.js + TypeScript, not Rust)
- Look for
-
If multiple technology files found:
- Ask user which stack to prioritize
- Store the detected stack
Output format:
✓ Stack Detected: [Technology Name]
Your project uses [Technology]. Claude Craft has specialized commands and agents for this stack.
Step 2: Propose 3 High-Impact Actions (1 minute)
Based on the detected stack, recommend 3 contextualized commands that provide immediate value.
Stack to Commands Mapping
Symfony / PHP:
/symfony:check-architecture— Verify Clean Architecture + DDD compliance/symfony:check-testing— Analyze test coverage and quality/symfony:check-security— OWASP Top 10:2025 security audit
React:
/react:check-code-quality— TypeScript, ESLint, code standards/react:accessibility-check— WCAG compliance audit/react:bundle-analyze— Identify bundle size issues
Python:
/python:check-code-quality— Ruff, type hints, PEP 8/python:check-security— Bandit security scan/python:type-coverage— MyPy/Pyright coverage analysis
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.
- 5d ago First seen · 349 lines · 11 tokens per session scan A f99d3c812a43
getting-started is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 2,587 once invoked, about $0.0001 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.