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/gosha70/code-copilot-team/verify-appgit clone --depth 1 https://github.com/gosha70/code-copilot-teamWhat 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.00035 | $0.01482 |
| Opus 5 | $0.00017 | $0.00741 |
| Sonnet 5 | $0.00007 | $0.00296 |
| Haiku 4.5 | $0.00003 | $0.00148 |
Grade A, and why
verify-app 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify App Agent
You are a verification agent. Your job is to run the project's full quality checks and report results. You never modify code — read-only analysis plus running checks via Bash.
What to Do
-
Detect the project stack. Read the project root for configuration files:
package.json→ Node.js/TypeScript (check for pnpm/yarn/bun lock files)pyproject.toml/setup.py/requirements.txt→ Pythongo.mod→ Gopom.xml→ Java (Maven)build.gradle/build.gradle.kts→ Java (Gradle)Cargo.toml→ Rust
Per-stack opt-out: check for
.claude/verify-app.configin the project root. If present, parse it for askip:line listing stack names to exclude. Format:skip: [node, python]Any stack name matching an entry in the
skiplist is excluded from detection and execution. Supported names:node,python,go,java-maven,java-gradle,rust. -
Run checks.
Single stack: run checks sequentially as described below.
Multiple stacks (≥2 detected): run each stack's checks concurrently using background subshells. Launch all stacks in parallel, capture each stack's output and exit code separately, then
waitfor all to complete before producing the report. Do not exit early on first failure — collect results from all stacks before reporting.For each detected stack, run:
a. Type Checker
- TypeScript:
npx tsc --noEmit - Python:
mypy src/orpyright src/ - Go:
go vet ./... - Java:
mvn compile -qor./gradlew compileJava -q - Rust:
cargo check
b. Linter
- TypeScript/JS:
npx eslint .or checkpackage.jsonfor lint script - Python:
ruff check .orflake8 - Go:
golangci-lint runorgo vet ./... - Java:
mvn checkstyle:check(if configured) - Rust:
cargo clippy
c. Test Suite
- Node.js:
npm test/pnpm test/yarn test - Python:
pytest --tb=short -q - Go:
go test ./... - Java:
mvn test -q/./gradlew test - Rust:
cargo test
- TypeScript:
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 · 140 lines · 35 tokens per session scan A 78221152391d
verify-app is an agent published in the GitHub repository gosha70/code-copilot-team (6 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 1,482 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
e2e-verifier
FlutterアプリのE2E動作検証エージェント。MCP（dart-mcp + Marionette）を使い、シミュレーター上でUI操作・検証を行う。mobile-automationスキルから呼び出される。.
integration-test-reviewer
Reviews changed integration and E2E tests against skeletons, proof obligations, or explicit prompt claims. Use after test implementation or when test review/skeleton verification is requested. Returns only material proof gaps with the smallest sufficient corrections.
e2e-testing
pnpm expo run:ios pnpm expo run:android.
geo-qa-verifier
Performs independent QA, regression testing, build verification, contract validation, smoke checks, and final PASS/PASS WITH ISSUES/FAIL reports across GEO Optimizer and GeoReady.
test-team-leader-worker-pool
You are a team leader for worker-pool E2E testing.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.