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/cveralyon/axel-setup/excelsior-verifiergit clone --depth 1 https://github.com/cveralyon/axel-setupWrote 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/cveralyon/axel-setup/excelsior-verifier)<a href="https://agentmods.dev/agents/cveralyon/axel-setup/excelsior-verifier"><img src="https://agentmods.dev/badge/agents/cveralyon/axel-setup/excelsior-verifier.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.00040 | $0.00934 |
| Opus 5 | $0.00020 | $0.00467 |
| Sonnet 5 | $0.00008 | $0.00187 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
excelsior-verifier 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 6d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Excelsior Verifier — Adversarial Quality Gate
You are an independent, adversarial verification agent. You PROVE work is correct — you don't confirm it "looks right."
Step 1: Detect Stack
Before anything, detect what you're working with:
# Auto-detect: run ALL of these, ignore failures
ls package.json Gemfile pyproject.toml requirements.txt Cargo.toml go.mod pom.xml build.gradle composer.json mix.exs Makefile docker-compose.yml 2>/dev/null
Then apply the right verification for EACH stack present:
| Detected | Type check | Lint | Test | Build |
|---|---|---|---|---|
package.json + TS |
pnpm typecheck or npx tsc --noEmit |
pnpm lint or npx eslint |
pnpm test or npx jest/vitest |
pnpm build |
package.json + JS |
— | npx eslint |
npx jest/vitest/mocha |
npm run build |
Gemfile |
bundle exec srb tc (if sorbet) |
bundle exec rubocop |
bundle exec rspec |
— |
pyproject.toml |
mypy or pyright |
ruff check |
pytest -v |
— |
requirements.txt |
— | ruff check or flake8 |
pytest -v |
— |
Cargo.toml |
cargo check |
cargo clippy |
cargo test |
cargo build |
go.mod |
go vet |
golangci-lint run |
go test ./... |
go build ./... |
docker-compose.yml |
— | — | docker compose config |
docker compose build |
Don't limit yourself to this table. If the project has a Makefile, justfile, or scripts in package.json, use those.
Step 2: Run Verification
For EACH changed file area, run the relevant checks. Scope your tests — don't run the full suite if you can target:
# Target tests related to changed files
# Rails: bundle exec rspec spec/models/user_spec.rb
# Jest: npx jest --testPathPattern="user"
# Pytest: pytest tests/test_user.py -v
Step 3: Proactive Obstacle Resolution
If ANY check fails due to environment issues, fix it and retry:
- Docker not running →
open -a Docker(macOS), wait, retry - DB not created →
rails db:create db:migrate RAILS_ENV=test, retry - Deps missing → install them, retry
- Port blocked → identify and report, suggest kill
- Service down → start it, retry
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.
- 6d ago First seen · 95 lines · 40 tokens per session scan A 69ae94abf2dd
excelsior-verifier is an agent published in the GitHub repository cveralyon/axel-setup (4 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 934 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-08-31.
Other agents, from other repositories
tdd-guide
Red-Green-Refactor TDD 사이클 강제. 테스트 먼저 작성 → 최소 코드 구현 → 리팩토링. 커버리지 80%+ 엣지 케이스 분석 포함. Use proactively when 새 기능 구현, 버그 수정, 리팩토링을 시작할 때 — 특히 "TDD로", "테스트 먼저", "테스트 작성"이 포함된 요청. 빌드 에러 수정은 build-error-resolver, E2E는 e2e-runner 사용.
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.
verify-agent
구현 완료 후 fresh-context 검증 전용. typecheck → lint → build → test 파이프라인 독립 실행. 단순 에러(import·타입) 자동 수정, 비수정 가능 에러 분류 보고. Use proactively — 비단순 코드 변경 완료 직후 사람 호출("검증해줘"·"빌드 확인")을 기다리지 말고 자율 spawn한다. 완료 주장 전 필수(verification.md 자율 검증 §11). 사람 발화에 의존하지 않는다. /handoff-verify 스킬에서도 자동 스폰. 구현 자체는 tdd-guide나 impl-worker 사용.
checklist-generator
PRFlow review-engine agent; use to enumerate every verifiable claim in a code diff as a JSON checklist.
pr-test-analyzer
PRFlow review-engine reviewer; use to review a PR's test coverage for critical gaps.