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/test-setupgit 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.00678 |
| Opus 5 | $0.00000 | $0.00339 |
| Sonnet 5 | $0.00000 | $0.00136 |
| Haiku 4.5 | $0.00000 | $0.00068 |
Grade C, and why
test-setup 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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Test PreToolUse Bash hook: echo "rm -rf /" → should block How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Setup — Verify Entire Claude Code Configuration
Run a comprehensive verification of the entire MEGA setup. This is the FIRST thing to run after dropping this template into a new project.
Tests:
1. File Structure Integrity
- Verify ALL agent files exist and have valid YAML frontmatter (name, description, tools, model)
- Verify ALL command files exist
- Verify settings.json is valid JSON with all required sections (hooks, env, permissions)
- Verify .mcp.json is valid JSON with all servers
- Verify .lsp.json is valid JSON
- Verify CLAUDE.md exists and has all required sections
2. Agent Consistency
- Every agent mentioned in CLAUDE.md exists as a file
- Every agent file has the correct model tier (opus/sonnet/haiku as documented)
- No agent has tools it shouldn't have (e.g., security-auditor should NOT have Write)
- All agents have an Output Format section
3. Command Consistency
- Every command that should have context: fork actually has it
- Expected fork commands: swarm, autopilot, conductor, compete, self-heal, review-with-fresh-eyes, nightly-scan, evolve
- Every command uses $ARGUMENTS at the end
- No command references an agent that doesn't exist
4. Hook Verification
- All hooks in settings.json are syntactically valid bash
- Test PreToolUse Bash hook: echo a safe command → should pass
- Test PreToolUse Bash hook: echo "rm -rf /" → should block
- Test PreToolUse Edit hook: simulate main branch → should block
- Verify Setup hook runs without errors
5. MCP Server Check
- For each server in .mcp.json: verify the npm package exists (npm view )
- Flag any servers with placeholder tokens (<YOUR_...)
- Report which servers are ready vs need configuration
6. Environment Variables
- Verify all env vars in settings.json are documented in CLAUDE.md
- Verify CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 is set
7. Cross-Reference Check
- bootstrap.sh mentions same number of agents/commands/MCP as actual files
- SUMMARY.md stats match actual file counts
- .gitignore covers all generated report directories
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 · 77 lines · 0 tokens per session scan C 290bc4623cac
test-setup 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 678 tokens. 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
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.