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 aiappsgbb/awesome-gbb --skill foundry-evalsgit clone --depth 1 https://github.com/aiappsgbb/awesome-gbbWrote 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/aiappsgbb/awesome-gbb/foundry-evals)<a href="https://agentmods.dev/skills/aiappsgbb/awesome-gbb/foundry-evals"><img src="https://agentmods.dev/badge/skills/aiappsgbb/awesome-gbb/foundry-evals.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 519 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00195 | $0.16077 |
| Opus 5 | $0.00097 | $0.08039 |
| Sonnet 5 | $0.00039 | $0.03215 |
| Haiku 4.5 | $0.00019 | $0.01608 |
Grade A, and why
foundry-evals scanned grade A with 1 finding 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 today.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| Grader returns 0 or 1 randomly across identical inputs | Grader is stateful (e.g., fetches live data, uses non-seeded randomness, or depends on current time). Evals require pure, deterministic functions. | Do not use n How it starts
The opening of the file, as written. The whole thing — 1,492 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Foundry Agent Evaluations
Evaluate Foundry hosted agents using the two-phase invoke+score pattern with Foundry's built-in evaluators.
For the complete per-agent adoption and release-evidence workflow, see
foundry-agentops. This skill remains
authoritative for deep evaluator configuration and dataset design; AgentOps
aggregates evidence and never replaces that evaluation contract.
When to Use
- After deploying a hosted agent, to measure quality
- Running batch evaluations against test scenarios
- Comparing agent performance across versions
- Validating that business rules (BR-XXX from SpecKit) are followed
Why Two Phases?
The Foundry SDK's azure_ai_agent target type does NOT correctly route to hosted
agent endpoints — it sends requests to the project endpoint instead of the agent's
dedicated endpoint. You must invoke the agent yourself, then score the results separately.
Phase 1: Invoke agent → collect responses
Phase 2: Score responses → Foundry evaluators
Critical requirement: MUST complete both phases sequentially. Skipping either phase will result in incomplete evaluations.
Phase 1: Invoke the Agent
from azure.ai.projects import AIProjectClient
from azure.identity import DefaultAzureCredential
project = AIProjectClient(
endpoint="<project_endpoint>",
credential=DefaultAzureCredential(),
allow_preview=True,
)
oai = project.get_openai_client(agent_name="my-agent")
# Warm up — single-shot ping is INSUFFICIENT for hosted agents that
# scale to zero (15min idle). Use the retry loop pattern below for any
# eval likely to hit a cold container. A single ping can return
# server_error in ~9s and make every scenario fail before the agent
# has even spun up.
print("Warming up...")
oai.responses.create(input="Hello", stream=False)
# MUST invoke each query SEQUENTIALLY (never concurrent)
# Concurrent requests overwhelm cold-start containers → empty responses
results = []
for query in test_queries:
response = oai.responses.create(input=query, stream=False)
results.append({
"query": query,
"response": response.output_text,
})
print(f"✓ {query[:50]}...")
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/data/sample_eval_dataset.jsonl 1.3 KB
- references/python/__init__.py 60 B runs code
- references/python/eval_runner.py 3.7 KB runs code
- references/python/last_run.py 3.6 KB runs code
- references/python/url_citation_grader.py 3.4 KB runs code
- references/upstream-pin.md 14 KB
- test-fixture/consumer_prompt.md 3.9 KB
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.
- today Changed · +5 lines e7086fef723d
- 8d ago First seen · 1,487 lines · 195 tokens per session scan A e49434aa6457
foundry-evals is a skill published in the GitHub repository aiappsgbb/awesome-gbb (5 stars, last pushed yesterday), licensed MIT. It adds 195 tokens to every session and 16,077 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.