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/TheLobbi/claudeWrote 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/thelobbi/claude/test)<a href="https://agentmods.dev/commands/thelobbi/claude/test"><img src="https://agentmods.dev/badge/commands/thelobbi/claude/test/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/thelobbi/claude/test"><img src="https://agentmods.dev/badge/commands/thelobbi/claude/test.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.00484 |
| Opus 5.5 | $0.00000 | $0.00194 |
| Sonnet 5.5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
test scanned grade A 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -f http://localhost:8080/health || exit 1 What it actually says
Run Tests
Execute the test suite for Golden Armada agents.
Instructions
Run the appropriate test commands based on what's being tested:
1. Python Unit Tests
```bash
Run all Python tests
python -m pytest tests/ -v
Run with coverage
python -m pytest tests/ --cov=deployment/docker --cov-report=term-missing
Run specific test file
python -m pytest tests/test_agent.py -v
Run tests matching pattern
python -m pytest tests/ -k "test_health" -v ```
2. Linting & Type Checks
```bash
Flake8 linting
python -m flake8 deployment/docker/ --max-line-length=100
Type checking (if mypy configured)
python -m mypy deployment/docker/ --ignore-missing-imports ```
3. Helm Chart Validation
```bash
Lint Helm chart
helm lint ./deployment/helm/golden-armada
Template rendering test
helm template golden-armada ./deployment/helm/golden-armada --debug
Dry run against cluster
helm install golden-armada ./deployment/helm/golden-armada -n agents --dry-run ```
4. Docker Build Test
```bash
Build all images (no push)
docker build -f deployment/docker/claude/Dockerfile -t golden-armada/claude-agent:test deployment/docker/claude/ docker build -f deployment/docker/orchestrator/Dockerfile -t golden-armada/orchestrator:test deployment/docker/orchestrator/ ```
5. Integration Tests
```bash
Start local services
docker-compose up -d
Wait for services
sleep 10
Run integration tests
curl -f http://localhost:8080/health || exit 1
Cleanup
docker-compose down ```
Options
- --verbose: Show detailed test output
- --coverage: Generate coverage report
- --quick: Run only fast unit tests
- --integration: Run integration tests (requires Docker)
Expected Output
Tests should pass with no failures. Coverage target: >80%
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 · 82 lines · 0 tokens per session scan A e6199932c332
test is a command published in the GitHub repository TheLobbi/claude (21 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 484 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other commands, from other repositories
implementar
Ejecutar tareas TDD fase por fase dentro de Docker hasta que todos los tests pasen.
session
Complete guide to managing pair programming sessions.
test-tdd
Run when user calls /test-tdd. Scans modified files, locates their corresponding unit/integration test suites, and runs them.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
test-audit
Writes a versioned TESTAUDIT.md; with --fix, quarantines the rot in gated, revertible commits. TRIGGER WHEN: auditing a test suite, measuring test health, finding dead or flaky or redundant tests, or diagnosing failure causes and proposing temporary quarantine. DO NOT TRIGGER WHEN: one module's tests are consolidated…
story-and-test
For the component(s) in scope.