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/liortesta/clawdagent/quickstartgit clone --depth 1 https://github.com/liortesta/ClawdAgentWhat 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.00000 | $0.00497 |
| Opus 5 | $0.00000 | $0.00249 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
quickstart 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 2d 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.
What it actually says
Quickstart — Interactive Project Onboarding
Guide the user through setting up this Claude Code template in their project. Ask questions, configure, and verify — step by step.
Process:
Step 1: Project Detection
- Scan the current directory
- Detect: language, framework, package manager, test framework, database
- Show findings and ask user to confirm/correct
Step 2: Configure CLAUDE.md
- Fill in the Architecture section with detected values
- Fill in Key Commands with actual commands (npm/pnpm/yarn)
- Ask: "What are the most important project conventions I should know?"
- Add answers to Project Conventions section
Step 3: Configure MCP Servers
- Ask which MCP servers to activate:
- GitHub: "Do you want me to manage GitHub issues/PRs? (need GITHUB_TOKEN)"
- Playwright: "Do you have a web UI to test?"
- PostgreSQL: "Do you use PostgreSQL? (need DATABASE_URL)"
- Brave Search: "Do you want web search capability? (need BRAVE_API_KEY)"
- Slack: "Do you want Slack notifications? (need SLACK_BOT_TOKEN)"
- For servers with tokens: ask user to provide them
- Disable unused servers (comment out in .mcp.json)
Step 4: Install Dependencies
- Run bootstrap.sh (or bootstrap.ps1 on Windows)
- Install project dependencies
- Install LSP servers if needed
Step 5: Verify Setup
- Run /test-setup to verify everything
- Fix any issues found
- Run /setup-project for full project configuration
Step 6: First Task
- Ask: "What's the first thing you want to build or fix?"
- Recommend the right command to start:
- New feature → "/plan [feature]"
- Bug fix → "/self-heal"
- Code review → "/review"
- Understand codebase → "/plan analyze the entire codebase"
Output at End:
## Quickstart Complete!
**Project**: [name]
**Stack**: [language + framework]
**Active MCP Servers**: [list]
**Agents Available**: [count]
**Commands Available**: [count]
**Recommended first steps:**
1. `/plan [your first task]`
2. Start building!
$ARGUMENTS
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.
- 2d ago First seen · 63 lines · 0 tokens per session scan A 3e84db79ce39
quickstart is a command published in the GitHub repository liortesta/ClawdAgent (11 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 497 tokens. 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
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.