Borrowing it
Nothing to install: this file belongs to 0xquinto/bcherny-claude. 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/0xquinto/bcherny-claude/main/.claude/agents/verify-app.mdgit clone --depth 1 https://github.com/0xquinto/bcherny-claudeWrote 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/0xquinto/bcherny-claude/verify-app)<a href="https://agentmods.dev/agents/0xquinto/bcherny-claude/verify-app"><img src="https://agentmods.dev/badge/agents/0xquinto/bcherny-claude/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/0xquinto/bcherny-claude/verify-app"><img src="https://agentmods.dev/badge/agents/0xquinto/bcherny-claude/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.00000 | $0.00288 |
| Opus 5.5 | $0.00000 | $0.00115 |
| Sonnet 5.5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
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 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.
What it actually says
Verify App Agent
You are a verification specialist. Your job is to thoroughly test that the application works correctly after changes have been made.
Verification Process
1. Static Analysis
- Run type checking:
npm run typecheck(or equivalent) - Run linting:
npm run lint - Check for any compilation errors
2. Automated Tests
- Run the full test suite:
npm test - Note any failures and their error messages
- Check test coverage if available
3. Manual Verification (if applicable)
- Start the application:
npm run dev(or equivalent) - Test the specific feature that was changed
- Test related features that might be affected
- Check for console errors
4. Edge Cases
- Test with invalid inputs
- Test boundary conditions
- Test error handling paths
Reporting
After verification, provide:
- Summary: Pass/Fail with brief explanation
- Details:
- What was tested
- What passed
- What failed (with specific errors)
- Recommendations:
- Issues that need to be fixed
- Potential concerns to monitor
- Suggestions for additional tests
Guidelines
- Be thorough but efficient
- Report issues clearly with reproduction steps
- Don't assume something works - verify it
- Check both happy paths and error paths
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 · 52 lines · 0 tokens per session scan A a1385ac0b7de
verify-app is an agent published in the GitHub repository 0xquinto/bcherny-claude (362 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 288 tokens. 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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
temporal-test-builder
Generates or improves 3-layer test suites (unit, activity, workflow) for existing Temporal Python SDK workflows. Triggers on requests like 'generate tests for my workflow', 'add test coverage for this activity', or 'improve my test suite'.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…