Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/brazil-bench/pourpoisenpx agentmods add skills/brazil-bench/pourpoise/evaluate-attemptWrote 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/brazil-bench/pourpoise/evaluate-attempt)<a href="https://agentmods.dev/skills/brazil-bench/pourpoise/evaluate-attempt"><img src="https://agentmods.dev/badge/skills/brazil-bench/pourpoise/evaluate-attempt/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/brazil-bench/pourpoise/evaluate-attempt"><img src="https://agentmods.dev/badge/skills/brazil-bench/pourpoise/evaluate-attempt.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.00036 | $0.07903 |
| Opus 5 | $0.00018 | $0.03952 |
| Sonnet 5 | $0.00007 | $0.01581 |
| Haiku 4.5 | $0.00004 | $0.00790 |
Grade A, and why
evaluate-attempt 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.
How it starts
The opening of the file, as written. The whole thing — 968 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evaluate Benchmark Attempt
Overview
This SOP evaluates a completed brazil-bench attempt against the spec.md requirements, capturing metrics for comparison across orchestration patterns. Supports both Python and Swift/iOS implementations.
Parameters
- attempt_repo (required): Repository name (e.g.,
attempt-3) - output_dir (optional, default:
./results): Where to write evaluation results
Steps
0. Detect Project Language
Identify the primary language/platform of the implementation.
Detection Commands:
cd ./reviews/{attempt_repo}
# Python indicators
ls pyproject.toml setup.py requirements.txt 2>/dev/null
# Swift/iOS indicators
ls Package.swift *.xcodeproj *.xcworkspace 2>/dev/null
# Check file extensions
find . -name "*.py" -not -path "./.venv/*" | head -5
find . -name "*.swift" | head -5
Language Detection Matrix:
| Files Found | Language | Test Framework |
|---|---|---|
pyproject.toml, *.py |
Python | pytest |
Package.swift, *.swift |
Swift Package | swift test |
*.xcodeproj, *.swift |
iOS/Xcode | xcodebuild test |
| Both Python and Swift | Multi-language | Run both |
Constraints:
- You MUST detect the language before running tests
- You MUST use appropriate commands for the detected language
- You SHOULD note the detected language in the report
1. Clone Attempt
Fetch the attempt repository for local analysis.
Constraints:
- You MUST clone into
./reviews/{attempt_repo} - You MUST verify the clone succeeded before proceeding
- You MUST NOT modify any files in the cloned repo
gh repo clone brazil-bench/{attempt_repo} ./reviews/{attempt_repo}
2. Verify Spec Integrity
Confirm the spec.md was not modified from the template.
Constraints:
- You MUST compare
spec.mdagainst the template version - You MUST fail the evaluation if spec.md was modified
- You SHOULD use a checksum comparison
gh repo clone brazil-bench/benchmark-template ./reviews/_template --depth 1
diff ./reviews/{attempt_repo}/spec.md ./reviews/_template/spec.md
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 · 968 lines · 36 tokens per session scan A 938f019791b5
evaluate-attempt is a skill published in the GitHub repository brazil-bench/pourpoise (11 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 7,903 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-08-30.
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.