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 skills add Open-Agent-Tools/General-OAT-Skills --skill run-adk-evalsgit clone --depth 1 https://github.com/Open-Agent-Tools/General-OAT-SkillsWrote 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/skills/open-agent-tools/general-oat-skills/run-adk-evals)<a href="https://agentmods.dev/skills/open-agent-tools/general-oat-skills/run-adk-evals"><img src="https://agentmods.dev/badge/skills/open-agent-tools/general-oat-skills/run-adk-evals/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/skills/open-agent-tools/general-oat-skills/run-adk-evals"><img src="https://agentmods.dev/badge/skills/open-agent-tools/general-oat-skills/run-adk-evals.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.00056 | $0.00494 |
| Opus 5 | $0.00028 | $0.00247 |
| Sonnet 5 | $0.00011 | $0.00099 |
| Haiku 4.5 | $0.00006 | $0.00049 |
Grade A, and why
run-adk-evals 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 11d 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
Run all Google Agent Development Kit (ADK) evaluations in the specified folder in numerical then alphabetical order with detailed results and failure summaries.
Usage: Specify the folder containing the ADK agent and evaluations (e.g., test_agent/)
Example:
/run-adk-evals my_agent/
This will run all evaluations in my_agent/evals/ directory in sorted order.
Prerequisites:
- Ensure required environment variables are set (e.g., GOOGLE_API_KEY, MCP server URLs)
- Any required services must be running
- ADK dependencies installed (
pip install -r requirements.txt)
Process:
- Validate Environment: Check required environment variables and dependencies
- Discover Evaluations: Find all *_test.json files in the evals/ directory
- Sort Execution Order: Numerical then alphabetical order (e.g., test_config.json, then alphabetical *_test.json)
- Run Each Evaluation: Execute
adk evalwith--print-detailed-resultsfor each test - Summarize Results: Provide detailed summary of all results and failure reasons
ADK Eval Command Format: For each evaluation, run:
PYTHONPATH=.:$PYTHONPATH adk eval \
--config_file_path {agent_folder}/evals/test_config.json \
--print_detailed_results \
{agent_folder} \
{agent_folder}/evals/{test_file}.json
Rate Limiting: Add 10-second delays between tests to avoid API limits. Use sequential execution only.
Output Format:
- Clear section headers with timestamps
- Individual test results with pass/fail status
- Detailed failure analysis for any failed evaluations
- Overall summary with statistics
Error Handling: Rate limiting delays between tests, comprehensive error reporting for troubleshooting.
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.
- 11d ago First seen · 57 lines · 56 tokens per session scan A 9e203888d093
run-adk-evals is a skill published in the GitHub repository Open-Agent-Tools/General-OAT-Skills (3 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 494 once invoked, about $0.0003 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 skills, from other repositories
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
ios-simulator
Verify and debug native, React Native, Expo, or Flutter apps on an iOS Simulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an iPhone or iPad Simulator.
solopi-ai
A command-line framework for testing Android apps and devices with SoloPi, including on-device or cloud AI decision models. It manages devices, test cases, recorded interactions, replays, performance history, and evidence.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
performing-api-fuzzing-with-restler
Uses Microsoft RESTler to perform stateful REST API fuzzing by automatically generating and executing test sequences that exercise API endpoints, discover producer-consumer dependencies between requests, and find security and reliability bugs. The tester compiles an OpenAPI specification into a RESTler fuzzing…
smoke-test
Run smoke tests against a deployed or local app based on your git diff. Each test uses Skyvern browser tools (navigate, act, validate, screenshot) with Chrome DevTools MCP as fallback. Posts screenshot evidence as PR comments.