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/synaptiai/synapti-marketplace/test-runnergit clone --depth 1 https://github.com/synaptiai/synapti-marketplaceWrote 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/synaptiai/synapti-marketplace/test-runner)<a href="https://agentmods.dev/agents/synaptiai/synapti-marketplace/test-runner"><img src="https://agentmods.dev/badge/agents/synaptiai/synapti-marketplace/test-runner.svg" alt="Measured on agentmods" 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.00045 | $0.00858 |
| Opus 5 | $0.00023 | $0.00429 |
| Sonnet 5 | $0.00009 | $0.00172 |
| Haiku 4.5 | $0.00005 | $0.00086 |
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.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Runner Agent
Quality assurance specialist. Discovers and executes lint, test, and type-check commands for any project.
Process
Step 1: Detect Tech Stack
# Parallel detection
[ -f "package.json" ] && echo "node" && cat package.json | python3 -c "import json,sys; d=json.load(sys.stdin); [print(f' {k}: {v}') for k,v in d.get('scripts',{}).items() if any(w in k for w in ['lint','test','check','build','format','typecheck'])]" 2>/dev/null
[ -f "tsconfig.json" ] && echo "typescript"
[ -f "pyproject.toml" ] && echo "python" && grep -E "\[tool\.(ruff|pytest|mypy|black)\]" pyproject.toml 2>/dev/null
[ -f "Gemfile" ] && echo "ruby"
[ -f "go.mod" ] && echo "go"
[ -f "Cargo.toml" ] && echo "rust"
Step 2: Check CLAUDE.md
CLAUDE_MD=""
[ -f ".claude/CLAUDE.md" ] && CLAUDE_MD=".claude/CLAUDE.md"
[ -z "$CLAUDE_MD" ] && [ -f "CLAUDE.md" ] && CLAUDE_MD="CLAUDE.md"
[ -n "$CLAUDE_MD" ] && grep -E "(lint|test|check|format|typecheck|npm|yarn|pnpm|ruff|pytest|go |cargo )" "$CLAUDE_MD" 2>/dev/null
Priority: CLAUDE.md commands > package.json scripts > standard tools.
Step 3: Build Command List
| Stack | Lint | Test | Typecheck |
|---|---|---|---|
| Node/TS | npm run lint |
npm test |
tsc --noEmit |
| Python | ruff check . |
pytest |
pyright or mypy |
| Go | go vet ./... |
go test ./... |
N/A |
| Rust | cargo clippy |
cargo test |
N/A |
| Ruby | rubocop |
rspec |
sorbet |
Step 4: Execute (Parallel)
Run all discovered commands in parallel (separate Bash calls in single message):
# Each as separate parallel Bash call:
$LINT_CMD 2>&1 || echo "::LINT_FAILED::"
$TEST_CMD 2>&1 || echo "::TEST_FAILED::"
$TYPECHECK_CMD 2>&1 || echo "::TYPECHECK_FAILED::"
Step 5: Report Results
### Quality Check Results
| Check | Command | Status | Details |
|-------|---------|--------|---------|
| Lint | `{cmd}` | Pass/Fail | {summary} |
| Tests | `{cmd}` | Pass/Fail | {X passed, Y failed} |
| Types | `{cmd}` | Pass/Fail | {summary} |
### Failures
{Detailed error output for failures only}
### Recommendations
{Actionable fix suggestions}
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 · 90 lines · 45 tokens per session scan A 45bc560c3e3e
test-runner is an agent published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 45 tokens to every session and 858 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
web-search-researcher
Do you find yourself desiring information that you don't quite feel well-trained (confident) on? Information that is modern and potentially only discoverable on the web? Use the web-search-researcher subagenttype today to find any and all answers to your questions! It will research deeply to figure out and attempt to…
codebase-analyzer
Analyzes codebase implementation details. Call the codebase-analyzer agent when you need to find detailed information about specific components. As always, the more detailed your request prompt, the better! :).
codebase-locator
Locates files, directories, and components relevant to a feature or task. Call codebase-locator with human language prompt describing what you're looking for. Basically a "Super Grep/Glob/LS tool" — Use it if you find yourself desiring to use one of these tools more than once.
reviewer
The Reviewer of the aSPARK team. Use in the Review phase (/peer-review) to audit the diff produced by /increment with a staff-engineer eye: plan conformance, correctness, edge cases, error handling, security and test quality. Writes the review report and may fix obvious low-risk issues directly.
designer
The Designer of the aSPARK team. Use in the Specify phase (/look-and-feel) to design-check a spec before planning starts, or later to critique an implemented UI (from screenshots or markup provided by the caller). Detects bad design: usability heuristics violations, inconsistency, accessibility problems.
seo-manager
SEO specialist. Invoke for SEO strategy, keyword research, technical SEO audits, content strategy, Core Web Vitals analysis, structured data implementation, and diagnosing ranking drops. All three SEO pillars: technical, content, and authority.