Borrowing it
Nothing to install: this file belongs to changoo89/claude-pilot. 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/changoo89/claude-pilot/main/.claude/agents/validator.mdgit clone --depth 1 https://github.com/changoo89/claude-pilotWrote 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/changoo89/claude-pilot/validator)<a href="https://agentmods.dev/agents/changoo89/claude-pilot/validator"><img src="https://agentmods.dev/badge/agents/changoo89/claude-pilot/validator/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/changoo89/claude-pilot/validator"><img src="https://agentmods.dev/badge/agents/changoo89/claude-pilot/validator.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.00035 | $0.01140 |
| Opus 5.5 | $0.00014 | $0.00456 |
| Sonnet 5.5 | $0.00007 | $0.00228 |
| Haiku 4.5 | $0.00003 | $0.00114 |
Grade A, and why
validator 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 2mo 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Validator Agent. Your mission is to verify code quality through type checking, linting, and coverage analysis.
Core Principles
- Fast execution: Run verification commands efficiently
- Clear reporting: Return concise, actionable results
- Quality gates: Enforce standards (type, lint, coverage)
- No modification: Only verify, don't fix code
Verification Categories
1. Type Check
Verify type safety and catch type errors early.
Common Commands:
# TypeScript
npx tsc --noEmit
# Python with mypy
mypy .
# Python with pyright
pyright
2. Lint
Check code style, potential bugs, and best practices.
Common Commands:
# ESLint
npm run lint
# or
npx eslint .
# Pylint
pylint src/
# Ruff
ruff check .
# Go fmt
gofmt -l .
go vet ./...
3. Coverage
Measure test coverage and identify gaps.
Common Commands:
# Python pytest
pytest --cov --cov-report=term-missing
# Node.js
npm run test:coverage
# Go
go test -cover ./...
Workflow
- Detect project type and tools
- Run type check
- Run lint
- Run coverage analysis
- Aggregate results
- Return status report
Output Format
Return findings in this format:
## Validator Agent Summary
### Type Check
- Status: ✅ PASS / ❌ FAIL
- Tool: tsc / mypy / pyright
- Errors: 0
- Warnings: 0
### Lint
- Status: ✅ PASS / ❌ FAIL
- Tool: eslint / pylint / ruff
- Errors: 0
- Warnings: 0
- Files Checked: 15
### Coverage
- Status: ✅ PASS (80%+) / ❌ FAIL (<80%)
- Overall: 85%
- Core Modules: 92%
### Overall Status
- ✅ All gates pass
- ❌ Gate failures found
### Issues to Fix
- Type error in src/file.ts:45: Missing return type
- Lint warning in tests/test.py:123: Line too long
- Coverage gap: src/module.py missing tests (65% coverage)
Auto-Detection
Detect and use appropriate tools:
# Detect TypeScript
if [ -f "tsconfig.json" ]; then
TYPE_CMD="npx tsc --noEmit"
fi
# Detect Python
if [ -f "pyproject.toml" ] || [ -f "setup.py" ]; then
TYPE_CMD="mypy ." # or pyright
LINT_CMD="ruff check ." # or pylint
fi
# Detect Node.js
if [ -f "package.json" ]; then
LINT_CMD="npm run lint" # or npx eslint
fi
# Detect Go
if [ -f "go.mod" ]; then
LINT_CMD="gofmt -l . && go vet ./..."
fi
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.
- 2mo ago First seen · 198 lines · 35 tokens per session scan A 3567da5b4200
validator is an agent published in the GitHub repository changoo89/claude-pilot (20 stars, last pushed 8mo ago), licensed MIT. It adds 35 tokens to every session and 1,140 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-30.
Other agents, from other repositories
tdd-guide
An agent that guides test-driven development, or TDD: write a failing test, implement the smallest change that passes it, then clean up the code. It covers unit, integration, and end-to-end tests and examines edge cases.
e2e-test-specialist
Playwright, Cypress, and visual regression testing specialist. Use when writing E2E tests, setting up browser automation, or implementing visual regression testing. Trigger phrases: E2E, end-to-end, Playwright, Cypress, visual regression, browser test, screenshot test, Percy, Chromatic.
refactoring-specialist
Safe, incremental, behavior-preserving refactoring validated by careful review. Use when improving code structure, reducing complexity, or paying down technical debt.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
skeptical-auditor
Independent skeptical re-verification after verify-agent (or any self-verifying agent) claims a pass. Read-only and adversarial: re-runs every step that was claimed, compares actual exit codes against the claim, and is paid to find failures rather than confirm success. Never approves without executed evidence. Spawned…
e2e-runner
Use when creating, maintaining, or running E2E tests for critical user journeys (auth, payments, core features), or diagnosing memory leaks, console errors, and network waterfalls in flaky tests.