bench-contribute

bench-contribute is a command for Claude Code from elbalen/skopus. It costs 13 tokens per session (972 once invoked), scanned A, original, MIT.

A command that turns your approved feedback files into anonymized benchmark scenarios. These scenarios test whether an AI agent continues to follow corrections from earlier sessions.

In plain words
What is it for?
Use it to create correction-persistence tests from feedback stored in ~/.skopus/memory/feedback/*.md and add new cases to the benchmark dataset.
Why use it?
It converts real mistakes and corrections into repeatable tests, while skipping corrections already represented in the dataset.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

Good fit Use it to create correction-persistence tests from feedback stored in /.skopus/memory/feedback/.md and add new cases to the benchmark dataset.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/elbalen/skopus/bench-contribute
Install

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.

Clone the repo
git clone --depth 1 https://github.com/elbalen/skopus

Made for: Claude Code.

Wrote 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.

agentmods badge for bench-contribute

README.md
[![agentmods](https://agentmods.dev/badge/commands/elbalen/skopus/bench-contribute.svg)](https://agentmods.dev/commands/elbalen/skopus/bench-contribute)
Your own site
<a href="https://agentmods.dev/commands/elbalen/skopus/bench-contribute"><img src="https://agentmods.dev/badge/commands/elbalen/skopus/bench-contribute.svg" alt="Measured on agentmods" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 972 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00013 $0.00972
Opus 5 $0.00006 $0.00486
Sonnet 5 $0.00003 $0.00194
Haiku 4.5 $0.00001 $0.00097

Measured 7d ago against content hash 2e5dedfdc6ee, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

bench-contribute 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 7d 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.

skopus/templates/commands/bench-contribute.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/bench-contribute

Turn your real corrections into benchmark scenarios that help measure whether AI agents actually learn from feedback. Your corrections are the most valuable training data because they're authentic — they came from real drift in real sessions.

This runs inside the agent, not the shell. The agent reads your feedback files and generates anonymized scenarios with your approval.

Steps

  1. Read all feedback files from ~/.skopus/memory/feedback/*.md. For each file, extract:

    • title — what the rule is
    • why — why it matters
    • how_to_apply — when and where it kicks in
  2. Check which corrections are already in the dataset. Read ~/skopus/bench/correction_persistence/dataset.json (or the installed package's copy). Skip any correction that already has a matching scenario (by charter_relevance field).

  3. For each NEW correction, generate a candidate scenario with these fields:

    {
      "id": "cp-NNN",
      "domain": "code | prose | reasoning | tool-use",
      "title": "<short title>",
      "initial_task": "<a realistic task where the agent would make this mistake>",
      "expected_mistake_pattern": "<what the agent typically gets wrong>",
      "correction": "<the correction, generalized to remove proprietary details>",
      "followup_task": "<a SIMILAR but DIFFERENT task to test if the correction persists>",
      "success_criterion": {
        "must_include": ["<keywords that indicate the correction was applied>"],
        "must_not_include": ["<keywords that indicate the mistake was repeated>"]
      },
      "charter_relevance": "<which charter non-negotiable this tests>"
    }
    
  4. Anonymize and generalize. Remove:

    • Company names, product names, internal tool names
    • Specific file paths, class names, variable names
    • Personal names, team member names
    • API keys, URLs, internal endpoints

    Replace with generic equivalents. "Don't use npm in the UEVA frontend Docker setup" becomes "Don't suggest local npm when the project uses Docker containers for the frontend."

Read the full file on GitHub · 87 lines

Changes

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.

  1. 7d ago First seen · 87 lines · 13 tokens per session scan A 2e5dedfdc6ee

Subscribe to this mod's changes

bench-contribute is a command published in the GitHub repository elbalen/skopus (4 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 972 once invoked, about $0.0001 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.