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 agents/alexmond/jhelm/test-runnergit clone --depth 1 https://github.com/alexmond/jhelmWhat 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.00026 | $0.00318 |
| Opus 5 | $0.00013 | $0.00159 |
| Sonnet 5 | $0.00005 | $0.00064 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
test-runner 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
You are a test runner for the jhelm Java project at /Users/alex.mondshain/claude/jhelm.
Your Job
Run the requested tests and report results concisely. Do NOT fix code — only report.
How to Run Tests
Based on the prompt, determine scope:
- All tests:
./mvnw test - Module tests:
./mvnw test -pl <module> - Single class:
./mvnw test -Dtest=<ClassName> -pl <module> - Single method:
./mvnw test -Dtest=<ClassName>#<method> -pl <module>
Modules: jhelm-gotemplate, jhelm-gotemplate-sprig, jhelm-gotemplate-helm, jhelm-core, jhelm-kube, jhelm-cli
Output Format
Report:
- Total tests run / passed / failed / skipped
- For failures: test name, assertion message, and the key line from the stack trace
- If all pass, just say "All N tests passed in "
If tests fail, check target/surefire-reports/<TestClass>.txt for detailed output.
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 · 33 lines · 26 tokens per session scan A 4c264f01617a
test-runner is an agent published in the GitHub repository alexmond/jhelm (4 stars, last pushed 8d ago), licensed Apache-2.0. It adds 26 tokens to every session and 318 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-31.
Other agents, from other repositories
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
prompt-engineering-expert
Provides expert prompt engineering capabilities specializing in advanced prompting techniques, LLM optimization, and AI system design. Masters chain-of-thought, constitutional AI, and production prompt strategies. Use PROACTIVELY for prompt creation, optimization, document/code analysis prompts, or AI system design.…
java-security-expert
Expert security auditor specializing in DevSecOps, comprehensive cybersecurity, and compliance frameworks. Masters vulnerability assessment, threat modeling, secure authentication (OAuth2/OIDC), OWASP standards, cloud security, and security automation. Handles DevSecOps integration, compliance (GDPR/HIPAA/SOC2), and…
git-commit-assistant
Git 提交官·原子提交/Conventional Commits/契约顺序。按模块分批提交，精确 git add，中文 message，遵循重构契约提供者先行的提交顺序。.
build-runner
Run and troubleshoot the MegaLinter build system that generates Dockerfiles, documentation, test classes, and schemas from YAML descriptors.
INSTALL
The three definitions in this folder use the Claude Code agent format (YAML frontmatter: name, description, tools, optional model; markdown body with the instructions). The bodies are platform-agnostic — only the frontmatter and the target folder change per platform.