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.
git clone --depth 1 https://github.com/liortesta/ClawdAgentWrote 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/liortesta/clawdagent/test-setup)<a href="https://agentmods.dev/commands/liortesta/clawdagent/test-setup"><img src="https://agentmods.dev/badge/commands/liortesta/clawdagent/test-setup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/liortesta/clawdagent/test-setup"><img src="https://agentmods.dev/badge/commands/liortesta/clawdagent/test-setup.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00678 |
| Opus 5.5 | $0.00000 | $0.00271 |
| Sonnet 5.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 1mo 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.
- 1mo 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 1mo 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
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.