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.
git clone --depth 1 https://github.com/gosha70/code-copilot-teamWrote 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/gosha70/code-copilot-team/verify-app)<a href="https://agentmods.dev/agents/gosha70/code-copilot-team/verify-app"><img src="https://agentmods.dev/badge/agents/gosha70/code-copilot-team/verify-app/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/gosha70/code-copilot-team/verify-app"><img src="https://agentmods.dev/badge/agents/gosha70/code-copilot-team/verify-app.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.01487 |
| Opus 5.5 | $0.00014 | $0.00595 |
| Sonnet 5.5 | $0.00007 | $0.00297 |
| Haiku 4.5 | $0.00003 | $0.00149 |
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 27d 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 — 141 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.
- 27d ago Changed · +1 lines 22c99fade61c
- 1mo 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 (7 stars, last pushed 18d ago), licensed MIT. It adds 35 tokens to every session and 1,487 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
qa-analyzer
Use this agent after cycle completion or when the user requests bug hunting and QA analysis. World-class QA analyst that finds bugs before users do — thinks like a confused user, power user, and malicious attacker. Documents each issue precisely so it can be filed as a bug. Context: User just completed a cycle and…
walkthrough-analyzer
Use this agent after cycle completion for cycles with UI stories, or when the user requests interactive usability testing. Acts like a real first-time user - clicks every button, checks every state transition, and reports what doesn't feel right. Browser-only - never reads source code. Context: Cycle with UI stories…
checker
Fresh-context adversarial verification of completed work. Give it the claimed outcome plus the relevant diff or paths; it independently reruns tests, exercises the affected flow, probes edge cases, and returns CONFIRMED or REFUTED. Read-and-run only; it never plans, edits, or fixes anything.
backend-testing-specialist
Expert consultant for testing strategies, test automation, and quality assurance for backend systems. Use proactively for analyzing testing requirements, designing test architectures, recommending QA frameworks, and providing comprehensive testing guidance for backend applications. Provides analysis and…
discovery-agent
The post-green exploration seat the verification architecture names last — "Discovery agent: roams only after green, time-boxed, findings become journeys or fix tasks — never gates." Spawned only once verification/suite-state.json reports every criterion green (or quarantined-and-accepted), never before; receives that…
tester
Use to write and run unit and integration tests following the testing pyramid and AAA structure. Proves results with verbatim test output, never a narrative claim.