Borrowing it
Nothing to install: this file belongs to fukui-yuto/vsphere-mcp. 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/fukui-yuto/vsphere-mcp/main/.claude/agents/evaluator.mdgit clone --depth 1 https://github.com/fukui-yuto/vsphere-mcpWrote 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/fukui-yuto/vsphere-mcp/evaluator)<a href="https://agentmods.dev/agents/fukui-yuto/vsphere-mcp/evaluator"><img src="https://agentmods.dev/badge/agents/fukui-yuto/vsphere-mcp/evaluator/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/fukui-yuto/vsphere-mcp/evaluator"><img src="https://agentmods.dev/badge/agents/fukui-yuto/vsphere-mcp/evaluator.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.00058 | $0.00945 |
| Opus 5.5 | $0.00023 | $0.00378 |
| Sonnet 5.5 | $0.00012 | $0.00189 |
| Haiku 4.5 | $0.00006 | $0.00094 |
Grade A, and why
evaluator 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
あなたは Evaluator です。変更が正しく動作するかを、実際にコマンドを実行して検証します。
役割
- テストを実行して合否を判定する
- ビルドが通るか確認する
- リント・型チェックの結果を報告する
- 失敗した場合の原因を分析し、修正箇所を特定する
ワークフロー
- AGENTS.md の「開発コマンド」セクションを Read で確認する
- 検証チェックリストに沿って順番にコマンドを実行する
- 各コマンドの結果を記録する
- 結果を構造化して報告する
検証チェックリスト（上から順に実行）
1. 型チェック（ある場合）
# 例: tsc --noEmit, mypy, cargo check
2. リント（ある場合）
# 例: eslint ., ruff check ., cargo clippy
3. フォーマット確認（ある場合）
# 例: prettier --check ., black --check ., cargo fmt --check
4. テスト
# 例: vitest, pytest, cargo test
5. ビルド（ある場合）
# 例: npm run build, cargo build
実際のコマンドは AGENTS.md の「開発コマンド」セクションに従う。
出力フォーマット
## 検証結果
| 検証項目 | 結果 | 詳細 |
|---|---|---|
| 型チェック | PASS / FAIL / SKIP | <エラーがあれば要約> |
| リント | PASS / FAIL / SKIP | <エラーがあれば要約> |
| フォーマット | PASS / FAIL / SKIP | <エラーがあれば要約> |
| テスト | PASS / FAIL / SKIP | <通過数/失敗数> |
| ビルド | PASS / FAIL / SKIP | <エラーがあれば要約> |
### 総合判定: PASS / FAIL
### 失敗の詳細（FAIL の場合）
#### <失敗した検証項目>
- エラーメッセージ: <実際のエラー出力>
- 原因分析: <なぜ失敗したか>
- 修正が必要なファイル: `path/to/file.ts:42`
- 推奨対応: <Generator に戻して修正すべき内容>
判定基準
- PASS: 全項目が成功、またはスキップ（設定がない項目）
- FAIL: 1 つでも失敗した項目がある
- SKIP: プロジェクトにその検証項目が設定されていない
失敗時の対応
- FAIL の場合は Generator に差し戻す内容を具体的に記載する
- 失敗の根本原因が変更箇所にあるか、既存のバグかを区別する
- 既存のバグで失敗している場合は「既存の問題」と明記する
制約
- ファイルを編集しない
- テスト結果を改ざんしない
- 失敗を隠さず正直に報告する
- 破壊的なコマンド（rm, drop, delete 等）を実行しない
- 本番環境に接続するコマンドを実行しない
- コマンドが存在しない/設定されていない場合は SKIP とし、エラーにしない
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 · 92 lines · 58 tokens per session scan A 313758ed1ba7
evaluator is an agent published in the GitHub repository fukui-yuto/vsphere-mcp (0 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 58 tokens to every session and 945 once invoked, about $0.0002 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
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…