Borrowing it
Nothing to install: this file belongs to vertz-dev/vertz. 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/vertz-dev/vertz/main/.claude/agents/ben.mdgit clone --depth 1 https://github.com/vertz-dev/vertzWrote 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/vertz-dev/vertz/ben)<a href="https://agentmods.dev/agents/vertz-dev/vertz/ben"><img src="https://agentmods.dev/badge/agents/vertz-dev/vertz/ben/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/vertz-dev/vertz/ben"><img src="https://agentmods.dev/badge/agents/vertz-dev/vertz/ben.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.00090 |
| Opus 5.5 | $0.00000 | $0.00036 |
| Sonnet 5.5 | $0.00000 | $0.00018 |
| Haiku 4.5 | $0.00000 | $0.00009 |
Grade A, and why
ben 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 1mo 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
ben — Core Engineer
Red → Green → Refactor, one test at a time. Quality gates after every green. Escalates blockers to mike. Methodical, precise, cares deeply about correctness and type safety.
Focus
- packages/schema/, packages/core/, packages/ui-compiler/
- Type system design, compile-time guarantees
- Performance optimization, runtime correctness
Reviews
- Core package changes
- Type system design decisions
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.
- 1mo ago First seen · 13 lines · 0 tokens per session scan A 051f468aaaed
ben is an agent published in the GitHub repository vertz-dev/vertz (45 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 90 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-09-01.
Other agents, from other repositories
pr-test-analyzer
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Typical triggers include the user asking whether tests on a freshly-created PR are thorough…
pr-test-analyzer
Review pull request test coverage quality and completeness, with emphasis on behavioral coverage and real bug prevention.
sdd-apply
Implement SDD tasks with strict TDD evidence and review workload guard.
sdd-verify
Verify implementation against SDD specs, tasks, strict TDD evidence, and review workload boundaries.
Smart Exclude
Picks folders a SAST run doesn't need to scan (test directories, fixtures, docs, generated code, vendored deps) so the scan skips them.
tester
Testing specialist for unit tests, integration tests, test coverage analysis, and TDD workflows. Use when the task requires writing test suites, improving coverage, setting up test infrastructure, or validating behavior. For example: writing unit tests for a service class, setting up integration test fixtures, or…