Borrowing it
Nothing to install: this file belongs to agno-agi/agentos-docker. 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/agno-agi/agentos-docker/main/.agents/skills/eval-and-improve/SKILL.mdgit clone --depth 1 https://github.com/agno-agi/agentos-dockerWrote 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/agno-agi/agentos-docker/eval-and-improve)<a href="https://agentmods.dev/skills/agno-agi/agentos-docker/eval-and-improve"><img src="https://agentmods.dev/badge/skills/agno-agi/agentos-docker/eval-and-improve.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.1 | $0.00074 | $0.01491 |
| Opus 5 | $0.00037 | $0.00745 |
| Sonnet 5 | $0.00015 | $0.00298 |
| Haiku 4.5 | $0.00007 | $0.00149 |
Grade A, and why
eval-and-improve 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 8d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- eval-and-improve — 100% identical, 0 lines differ
- eval-and-improve — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eval and Improve
Coding-agent workflow: run as
/eval-and-improveor by describing the task.
Run the suite, diagnose every failure, fix what's in scope, stop when green. Cases live in evals/cases.py (agno.eval.Case), the setup/teardown sweeps in evals/hooks.py, the entrypoint in evals/__main__.py. Each case uses an LLM judge (criteria), a tool-call assertion (expected_tool_calls), and/or a deterministic scorer.
0. Preconditions
- Postgres on 5432 (
nc -z localhost 5432; elsedocker compose up -d agentos-db). - Venv active (
source .venv/bin/activate;./scripts/venv_setup.shif missing). No server needed — cases import the components directly. .envhasOPENAI_API_KEY(andPARALLEL_API_KEYif you use one — it pins Agno's expected web tool name at import). Worktrees don't inherit.env.
1. Run
python -m evals --tag smoke # fast template checks
python -m evals --tag release # broader pre-release checks
python -m evals --tag live # current web/source checks
python -m evals --name <case> # one case
python -m evals --tag smoke --list # what a selector picks, without running
python -m evals --json-output out.json # machine-readable (carries judge_reason)
python -m evals -v # stream the runs
Exit 0 = all passed. Be the only writer: teardowns sweep by snapshot diff, so a note or entity a teammate files during a case gets deleted. Coming from a scheduled failure? Find the case in eval history (db.get_eval_runs(), os.agno.com, or Platform Manager) and reproduce it with --name first; one that won't reproduce is usually environment. Stderr noise at the end of a run (Event loop is closed, httpx timeouts) is harmless.
2. Diagnose
| Symptom | Likely cause | Fix |
|---|---|---|
| Judge: right answer, missing X | Instructions don't push for X | agents/<slug>.py — tighten the rule |
| Judge: fabricated | Should have said it didn't know | Add a "say so plainly" rule |
| Reliability: missing tool | Routing rule weak, or the case too narrow | Strengthen the rule, or broaden expected_tool_calls |
Reliability: additional tool with allow_additional_tool_calls=False |
Agent fanned out | Tighten instructions or allow it |
Agno web tool name mismatch (parallel_search ↔ web_search) |
PARALLEL_API_KEY differs between .env and shell |
Sync and re-run |
| Flips PASS/FAIL across runs, no change | Judge variance | Re-run 2–3×; still flipping → make criteria more falsifiable |
| Fails in the suite, passes alone | Transient flake / 429 | Re-run alone, then the suite; persistent 429s → back off |
| Many fail at once | Broad regression (model, MCP down, tool removed) | Find the root cause; no prompt edits |
run paused awaiting user input |
Hit a HITL gate (Builder archive/delete) — never graded | Keep the case input on the ungated side |
cleanup: in the error |
A teardown couldn't delete what the case created | Hard-delete by id (eval_db.delete_component(id, hard_delete=True), ScheduleManager(eval_db).delete(id), eval_db.delete_learning(id), notes.delete(path)); don't touch the agent or case |
refusing to sweep … |
A guard tripped: rows predate the snapshot, or more rows than a case plausibly creates | Don't loosen the guard; inspect, delete the case's rows by hand, re-run |
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.
- 8d ago First seen · 79 lines · 74 tokens per session scan A 43455a1b1ede
eval-and-improve is a skill published in the GitHub repository agno-agi/agentos-docker (7 stars, last pushed 7d ago), licensed Apache-2.0. It adds 74 tokens to every session and 1,491 once invoked, about $0.0004 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
starlark-dev
Develop and debug Kurtosis Starlark packages. Create packages from scratch, understand the plan-based execution model, use print() debugging, handle future references, and test packages locally. Use when writing or troubleshooting .star files.
cli-local-build
Build and test the Kurtosis CLI from source. Compile the CLI binary locally, run it against Docker or Kubernetes engines, and iterate on CLI changes without creating a release. Use when developing or debugging CLI commands.
testing
· Write/debug tests: unit, integration, E2E, TDD, mocks, fixtures, a11y, perf. Triggers: 'test', 'test spec', 'TDD', 'playwright', 'vitest', 'jest', 'pytest', 'coverage', 'flaky'. Not for security tests (use security-audit).
代码调试
A debugging workflow that reproduces a problem with a failing test, collects evidence, finds the underlying cause, applies a fix, and runs regression checks. Regression checks verify that the fix does not break behavior that already worked.
dstest
Deterministic simulation testing for containerized services. Write Lua scripts to inject chaos (pause, kill, resource deprivation) into Docker containers with reproducible, seeded fault injection. Use when writing chaos experiments, testing service resilience, or debugging distributed systems.
Pair Programming
AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with…