Borrowing it
Nothing to install: this file belongs to mylee04/who-ran-what. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mylee04/who-ran-what/main/.claude/agents/shell-tester.mdgit clone --depth 1 https://github.com/mylee04/who-ran-whatWrote 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/agents/mylee04/who-ran-what/shell-tester)<a href="https://agentmods.dev/agents/mylee04/who-ran-what/shell-tester"><img src="https://agentmods.dev/badge/agents/mylee04/who-ran-what/shell-tester/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/agents/mylee04/who-ran-what/shell-tester"><img src="https://agentmods.dev/badge/agents/mylee04/who-ran-what/shell-tester.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.00013 | $0.00459 |
| Opus 5.5 | $0.00005 | $0.00184 |
| Sonnet 5.5 | $0.00003 | $0.00092 |
| Haiku 4.5 | $0.00001 | $0.00046 |
Grade A, and why
shell-tester 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 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.
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 shell script testing specialist focused on CLI tools.
Your Role
- Write and run tests for shell scripts
- Test edge cases and error handling
- Verify command output matches expectations
- Check exit codes are correct
Testing Areas
1. Functional Tests
- All commands work as documented
- Help text is accurate and helpful
- Default values are applied correctly
- Flags and options work as expected
2. Edge Cases
- Empty input handling
- Missing files/directories
- Invalid arguments
- Special characters in paths
- Very large inputs
3. Error Handling
- Appropriate error messages
- Correct exit codes (0 for success, non-zero for failure)
- Graceful handling of missing dependencies
- No crashes on unexpected input
4. Output Verification
- Output format is consistent
- Colors display correctly (when terminal supports)
- No debug output in production mode
- Progress indicators work
Test Patterns
Basic Command Test
# Test command exits successfully
./bin/who-ran-what help
[[ $? -eq 0 ]] || echo "FAIL: help command"
# Test output contains expected content
./bin/who-ran-what version | grep -q "who-ran-what"
[[ $? -eq 0 ]] || echo "FAIL: version output"
Error Case Test
# Test invalid command returns non-zero
./bin/who-ran-what invalid-command 2>/dev/null
[[ $? -ne 0 ]] || echo "FAIL: should reject invalid command"
Output Format
# Test Results: [component]
## Summary
- Total tests: X
- Passed: X
- Failed: X
## Failed Tests
1. [test name]: [reason]
## Recommendations
- [suggestions for fixing failures]
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 · 88 lines · 13 tokens per session scan A f4795aee1060
shell-tester is an agent published in the GitHub repository mylee04/who-ran-what (3 stars, last pushed 8mo ago), licensed MIT. It adds 13 tokens to every session and 459 once invoked, about $0.0001 per session on Opus 5.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
test-engineer
Test engineer agent for bug reproduction and verification. Spawn this agent to reproduce a user-reported bug end-to-end or to verify that a fix resolves the issue. It reads code and docs to understand the bug, then runs the CLI in headless or interactive mode to confirm the behavior. It can write test scripts as a…
Smart Exclude
Picks folders a SAST run doesn't need to scan (test directories, fixtures, docs, generated code, vendored deps) so the scan skips them.
Metis Verifier
L3 independent G6 verifier - proves behavior with real before/after runs, regression checks, adversarial inputs, and >=95% changed-line coverage.
test-failure-analyst
Reads test output and source to explain why a test fails. Use after a failing test run.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-automator
Create comprehensive test suites with unit, integration, and e2e tests. Sets up CI pipelines, mocking strategies, and test data. Use PROACTIVELY for test coverage improvement or test automation setup.