benchmark

A command that runs TRIZBENCH, an evaluation suite for inventive problem-solving across 12 standard engineering problems.

In plain words
What is it for?
Use it to evaluate reasoning on selected TRIZBENCH problems and score the resulting solutions.
Why use it?
It provides a structured way to assess how well proposed solutions identify contradictions, choose solution principles, and resolve the problem.

Command

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.

agentmods
npx agentmods add commands/sharathsphd/triz-engine/benchmark
Clone the repo
git clone --depth 1 https://github.com/SharathSPhD/triz-engine
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 609 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00011 $0.00609
Opus 5 $0.00005 $0.00304
Sonnet 5 $0.00002 $0.00122
Haiku 4.5 $0.00001 $0.00061

Measured yesterday against content hash f0463a498702, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

benchmark 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 yesterday.

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.

triz-engine/commands/benchmark.md · 62 lines

How it starts

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

You are the TRIZBENCH Runner. Execute the TRIZ benchmark suite to evaluate inventive reasoning quality against 12 canonical problems.

TRIZBENCH SCORING MODEL

Solutions are evaluated across 5 weighted dimensions (total 0-100):

Dimension Weight What It Measures
Contradiction Identification (CI) 25% Correct type + parameter mapping
Principle Selection (PS) 20% Jaccard similarity to target principles
Solution Novelty (SN) 20% non_obvious > novel_combination > standard > restatement
Contradiction Resolution (CR) 25% eliminates > reduces > manages > fails
IFR Proximity (IFR) 10% 0-4 scale against Ideal Final Result criteria

WORKFLOW

1. PROBLEM SELECTION

Present the user with the 12 TRIZBENCH problems or let them select a subset:

  • TB-01 through TB-12, spanning distributed systems, security, ML, API design, DevOps, privacy, IoT, search, compilers, org design, networking, and AI safety

2. ANALYSIS

For each selected problem:

  1. Run the full /triz:analyze pipeline (contradiction-agent → solution-agent → evaluator-agent)
  2. Capture the structured output (contradiction card, solution sketches, evaluator scores)

3. SCORING

Score the submission against the ground truth for each problem:

  • CI: Compare identified contradiction type and TRIZ parameters against ground truth
  • PS: Compute Jaccard similarity between selected and target principles
  • SN: LLM-as-judge assessment of solution novelty (single rubric prompt with calibration examples)
  • CR: LLM-as-judge assessment of contradiction resolution level
  • IFR: Use score_solution tool output (0-4 scale)

4. OUTPUT FORMAT

{
  "problem_id": "TB-XX",
  "participant": "[email protected]",
  "scores": {
    "ci": <0-100>,
    "ps": <0-100>,
    "sn": <0-100>,
    "cr": <0-100>,
    "ifr": <0-100>
  },
  "final_score": <weighted 0-100>,
  "details": {
    "contradiction_type": "...",
    "principles_applied": [...],
    "top_solution_summary": "..."
  }
}

Read the full file on GitHub · 62 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. yesterday First seen · 62 lines · 11 tokens per session scan A f0463a498702

Subscribe to this mod's changes

benchmark is a command published in the GitHub repository SharathSPhD/triz-engine (4 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 609 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.