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/ihsaan-ullah/auto-codabench/autocodabench-implementnpx skills add ihsaan-ullah/auto-codabench --skill autocodabench-implementgit clone --depth 1 https://github.com/ihsaan-ullah/auto-codabenchWrote 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/ihsaan-ullah/auto-codabench/autocodabench-implement)<a href="https://agentmods.dev/skills/ihsaan-ullah/auto-codabench/autocodabench-implement"><img src="https://agentmods.dev/badge/skills/ihsaan-ullah/auto-codabench/autocodabench-implement.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.00122 | $0.05672 |
| Opus 5 | $0.00061 | $0.02836 |
| Sonnet 5 | $0.00024 | $0.01134 |
| Haiku 4.5 | $0.00012 | $0.00567 |
Grade A, and why
autocodabench-implement 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 4d 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 — 502 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AutoCodabench — Phase 2: Competition Creation (self-validating)
You are running in Phase 2. Phase 1 saved an
implementation_plan.md covering all 7 design sections. Your job is
twofold:
- Write a complete Codabench bundle from that plan.
- Self-validate it: run the bundle's own baseline submission AND execute the starting-kit notebook end-to-end, both inside the bundle's declared Docker image. Iterate on runtime errors until both succeed.
This is a strict pipeline. A bundle that lints clean but whose own baseline can't run is a broken bundle — the iteration loop catches that class of defect before any downstream evaluator touches it.
You did NOT participate in Phase 1. The plan markdown is your single source of truth.
0. Hard rules
- Read first, write second. First three operations, in order:
The plan is locked: don'tautocodabench_current_run() Read("<run>/specs/implementation_plan.md") # or "<run>/implementation_plan.md" autocodabench_log_event(kind="stage_started", payload={"stage": "8.bundle"})snapshot_specto overwrite it. - No design decisions. Don't pick a different metric, change the splits, swap the baseline. If the plan is ambiguous, pick a sensible default and mention it in the closing message.
- Validate before zipping.
autocodabench_validate_bundleMUST return clean before you callautocodabench_zip_bundle. Fix the specific issues it flags; don't paper over them. - STRICT EXIT. Both the baseline run AND the starting-kit
notebook must finish with
ok: truebefore you zip. If afterMAX_ATTEMPTSyou can't get both green, mark the bundle asvalidate_runtime: falsein your closing message and DO NOT zip. A bundle whose own baseline can't run shouldn't ship. - Adapt code, not behavior. When iterating on a runtime failure,
you may:
- change the bundle's
docker_imageto one that ships a missing dependency (run-time installation is not available under Docker-only execution), - port an API call that broke (
tf.keras.optimizers.legacy.Adam→tf.keras.optimizers.Adam) by editing the bundle file, - tighten a path / file-naming bug in
score.py/ingestion.py.
- change the bundle's
What ships with it
1 file 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.
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.
- 4d ago First seen · 502 lines · 0 tokens per session scan A 6c2b57a2a3b1
autocodabench-implement is a skill published in the GitHub repository ihsaan-ullah/auto-codabench (2 stars, last pushed 1mo ago), licensed MIT. It adds 122 tokens to every session and 5,672 once invoked, about $0.0006 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
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and generates guidance to design and deploy a governed, secure agentic-analytics solution for data that's distributed across Google Cloud, other cloud providers, or on-premises. Data that's outside Google Cloud (such as data from Databricks, Snowflake, Salesforce, SAP, or Oracle systems) is…
training-check
Interactively monitor training metrics from the current Codex session, periodically checking WandB or fallback logs for NaN, divergence, plateaus, and broken runs.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.