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 agentmods add skills/githits-com/githits-cli/braintrust-agent-evalsnpx skills add githits-com/githits-cli --skill braintrust-agent-evalsgit clone --depth 1 https://github.com/githits-com/githits-cliWrote 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/githits-com/githits-cli/braintrust-agent-evals)<a href="https://agentmods.dev/skills/githits-com/githits-cli/braintrust-agent-evals"><img src="https://agentmods.dev/badge/skills/githits-com/githits-cli/braintrust-agent-evals.svg" alt="Measured on agentmods" 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 | $0.00031 | $0.02188 |
| Opus 5 | $0.00015 | $0.01094 |
| Sonnet 5 | $0.00006 | $0.00438 |
| Haiku 4.5 | $0.00003 | $0.00219 |
Grade A, and why
braintrust-agent-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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Braintrust agent evals
Use this skill for read-only inspection of the GitHits agent-eval history in the
Braintrust project githits-cli-agent-evals, or when the user explicitly asks
to export a validated local suite. The normalized exporter stores one top-level
eval span per scenario/workload cell plus structural tool children; see
docs/implementation/agentic-eval-metrics.md
for the field contract.
The persistence unit is one exporter invocation = one experiment, one
scenario/workload cell = one eval row, and one normalized logical tool call =
one structural tool child. Current exporter-owned experiment names are
main-r<run-id>-a<attempt>, pr-<pr-number>-r<run-id>-a<attempt>, and
local-<branch-slug>-<UTC-timestamp-with-milliseconds>-<short-sha>. Historical
github-* experiments predate this identity contract and should be treated as
historical evidence, not as current names or baseline candidates.
Safety and interpretation
- Read-only is the default. Never delete experiments or upload raw stdout, stderr, environment/configuration, provider events, or arbitrary artifacts.
- Never read or print
BRAINTRUST_API_KEY,.bt/, Keychain contents, or any credential/environment value. CI scopes the key only to its exporter step. - Do not treat an agent's self-reported confidence as result quality. This phase has no scorer or quality score.
- A failed or partial cell can be valid history when its normalized evidence is complete; distinguish that from a rejected suite or failed preflight.
Inspect experiments
Use the exercised project-option placement for list/view:
bt experiments --json --project githits-cli-agent-evals list
bt experiments --json --project githits-cli-agent-evals view <experiment-name>
Use the experiment ID returned by the view result for a bounded field query:
bt sql --json --non-interactive "SELECT input, output, metrics, metadata, tags FROM experiment('<experiment-id>') WHERE span_attributes.type = 'eval' LIMIT 23"
bt sql --json --non-interactive "SELECT name, span_attributes.type, metrics, metadata FROM experiment('<experiment-id>') WHERE span_attributes.type = 'tool' LIMIT 100"
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 First seen · 172 lines · 31 tokens per session scan A b97d98754c26
braintrust-agent-evals is a skill published in the GitHub repository githits-com/githits-cli (93 stars, last pushed today), licensed Apache-2.0. It adds 31 tokens to every session and 2,188 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
organize
Open the Cross-Code Organizer (CCO) dashboard — view and manage all memories, skills, MCP servers, hooks, and configs across scopes.
codestory-grounding
Use when an agent should ground a local repository with CodeStory before making source claims, planning edits, choosing tests, reviewing changes, or using broad retrieval evidence through the CodeStory plugin MCP.
ai-unity-asset-pipeline
Build, install, run, and verify a reusable image-to-game-ready-3D pipeline for Unity with controlled ImageGen references, approved AI mesh providers, Blender MCP/CLI, modular era catalogs, Blender retopology/LOD/pivot processing, and Unity import/render proof. Use for 2D-to-3D assets, vehicles, aircraft, ships…
source-command-cb-usage
코드브레인 활동 — Codex+Codex 토큰 + hook/MCP breakdown + PreToolUse 차단 횟수.
source-command-cb-health
코드브레인 상태 한 줄 요약 — doctor·큐·worker·인덱스.
coograph-apply
Implement tasks from an OpenSpec change. Use when the user wants to start or continue implementing a proposed change.