przeprogramowani

10x Bench Kit — AI skill for Claude Code

AI community

Create your own benchmark for coding AI Agents.

How to install 10x Bench Kit

This entry records only its repository, not the path inside it, so there is no exact command to give. Open przeprogramowani/10x-bench-kit and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What 10x Bench Kit does

Create your own benchmark for coding AI Agents.

Alternatives in AI

  • Graphify — AI coding assistant skill (Claude Code, Codex, OpenCode, OpenClaw, Factory Droid, Trae) 20.9k ★
  • Kilocode — GitHub Repo stars Open Source AI coding assistant for planning, building, and fixing code Open source AI assis 17k ★
  • Context Engineering Intro — GitHub Repo stars Context engineering - the new way of AI coding assistants Context engineering guide 12.8k ★

README

![](./benchkit.png)

10x-bench-kit

Template repo for an internal AI agent benchmark. This repo is the basis for a company's **benchmark instance**, created with [10xCLI](https://github.com/przeprogramowani/10x-cli) (`10x bench-kit init`) — a separate repo that holds the tasks, the evaluation pool, the configuration, and the results, and runs agent trials against the company's product repositories in full isolation.

**The benchmark is local-first.** Attempts and evaluations run on the operator's machine (or a VPS — same thing: a long-lived host with a container engine). GitHub Actions is plain CI/CD: readiness checks and leaderboard publication — never paid execution.

Initial harness: **OpenCode** (exclusively). Measured: quality (execution guards + LLM-as-judge-with-tools), cost, and execution time.

Prerequisites

  • 10xCLI — no global install needed (npx @przeprogramowani/10x-cli bench-kit init ).
  • A container engine: Docker Desktop or Podman.
  • Node.js >= 20.
  • Provider API keys in the shell environment (e.g. OPENROUTER_API_KEY).

Three zones

The repo structure is split into zones with different owners and different behavior during `10x bench-kit update`:

Zone Owner On update
.bench-kit/ kit (us) replaced wholesale (atomic)
.agents/skills/ shared proposed diff — the company decides
tasks/, evaluation-pool/, bench.config.yaml, results/, attempts/ company untouchable

Details of each zone's contract live in that zone's README.

Execution and evaluation are two independent processes

The core design decision (see `.bench-kit/ATTEMPT_FORMAT.md` for the full contract):

  1. bench attempt executes trials in throwaway containers and produces preserved attemptsattempts///trial-N/ with attempt.json, patch.diff, agent.log, metrics.json (cost and tokens read from the trial's local OpenCode storage