benchmark-methodology

benchmark-methodology is a skill for Claude Code, Codex from affaan-m/ECC. It costs 72 tokens per session (2,219 once invoked), scanned A, original, MIT.

A method for comparing competitors using the same nine weighted criteria, such as positioning, communication style, pricing, evidence, and enterprise readiness. Each criterion uses a defined 1–5 scoring scale.

In plain words
What is it for?
Use it after defining a competitor set to score companies, create comparable profile cards, and identify where a client could stand apart.
Why use it?
It replaces gut-feel rankings with scores tied to consistent evidence. This makes differences between competitors easier to explain and defend.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents).

Part of the ecc plugin — 70 skills, 56 commands, 68 agents, 1 MCP server shipped together

Good fit Use it after defining a competitor set to score companies, create comparable…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/affaan-m/ecc/benchmark-methodology
About the project

ECC is a toolkit that organizes and improves how coding agents work through skills, memory, security checks, research practices, and related extensions. It is for developers using agents such as Claude Code, Codex, OpenCode, and Cursor.

affaan-m/ECC · 250,130 stars · on GitHub · ecc.tools

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.

Any agent
npx skills add affaan-m/ECC --skill benchmark-methodology
Clone the repo
git clone --depth 1 https://github.com/affaan-m/ECC

Made for: Claude Code, Codex.

Or install ecc, the plugin that ships this one along with the rest of its 70 skills, 56 commands, 68 agents, 1 MCP server.

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 benchmark-methodology

README.md
[![agentmods](https://agentmods.dev/badge/skills/affaan-m/ecc/benchmark-methodology.svg)](https://agentmods.dev/skills/affaan-m/ecc/benchmark-methodology)
Your own site
<a href="https://agentmods.dev/skills/affaan-m/ecc/benchmark-methodology"><img src="https://agentmods.dev/badge/skills/affaan-m/ecc/benchmark-methodology.svg" alt="Measured on agentmods" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,219 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. ✓ AI security review Fable 5.1 · 6 Sept 2026
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.00072 $0.02219
Opus 5 $0.00036 $0.01110
Sonnet 5 $0.00014 $0.00444
Haiku 4.5 $0.00007 $0.00222

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

Security

Grade A, and why

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

Origin

Copies of this mod

4 near-identical copies found in the catalogue:

.agents/skills/benchmark-methodology/SKILL.md · 191 lines

How it starts

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

Benchmark Methodology

Use this skill to turn a scoped competitor set into comparable, defensible scores. Each competitor is assessed on the same nine dimensions, with explicit 1–5 rubrics, then captured in a uniform profile card. Consistency is the point: scores are only useful if the same evidence would earn the same number for any competitor.

When to Activate

  • A scoped, tiered competitor set from competitive-platform-analysis is ready to score.
  • Need comparable, evidence-anchored scores across competitors — not gut-feel rankings.
  • Client's strategic tension (the paired axes defining their target white-space) has been established.
  • Preparing to produce profile cards for assembly in competitive-report-structure.

Client positioning brief (establish first)

Before scoring, establish the client's positioning brief. It supplies:

  • Strategic tension — the two axes (e.g., memorability × hireability) whose intersection marks the client's target white-space. Dimension 9 is always the client's named tension; report both poles separately, never averaged.
  • Differentiator — what makes the client's moat. This informs which dimensions matter most for the client's positioning argument.
  • Brand balance — the intended mix of distinct strategic emphases. Strategic recommendations must not break this balance without flagging it.

Why these dimensions

The client competes on a specific tension held across two poles, not on service breadth. The dimensions are weighted to reflect that moat. Two dimensions — the tension poles — are scored separately and never averaged together, because the client's strategic question is precisely whether a rival achieves both simultaneously.

The nine dimensions (with weights)

Weights guide synthesis emphasis, not a single blended score (avoid a false composite — see Bias controls). Sum = 100%.

  1. Positioning clarity & distinctiveness (18%) — Is the studio's position sharp, ownable, and instantly legible? Or generic?
  2. Brand voice / verbal distinctiveness (15%) — Does the copy have an ownable register, or is it interchangeable agency-speak?
  3. Visual identity & site craft (15%) — Quality and ownership of the visual system; site as proof-of-craft.
  4. Service offer & packaging (12%) — Productized and legible (named sprints/audits) vs vague. Packaging maturity.
  5. Evidence & credibility (12%) — Named clients, quantified outcomes, case-study depth. Proof beyond assertion.
  6. Enterprise-readiness / commercial maturity (10%) — Signals they can land and hold SaaS/fintech/B2B/enterprise work (process, logos, scale, contracts).
  7. Thought leadership / content presence (8%) — Owned POV: writing, talks, newsletters, frameworks. Depth over volume.
  8. Pricing transparency & engagement model (5%) — Is pricing/engagement legible? Productized vs bespoke vs opaque.
  9. [Client's strategic tension] (5% as a flag; score BOTH poles, report separately) — Read the tension name and axis descriptions from the client's positioning brief. Plot both; the gap is the insight. The client's target quadrant is the single most important finding: who else is already there?

Read the full file on GitHub · 191 lines

Files

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.

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 · 191 lines · 72 tokens per session scan A a4ac232387a4

Subscribe to this mod's changes

benchmark-methodology is a skill published in the GitHub repository affaan-m/ECC (250,130 stars, last pushed yesterday), licensed MIT. It adds 72 tokens to every session and 2,219 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-30.

Related

Other skills, from other repositories

optimise-seo

Implements Next.js crawlability, metadata, canonicals, status codes, JSON-LD, hreflang, and crawler policy with served-page evidence. Use when asked to "fix SEO", "add a sitemap", "fix soft 404s", or "add llms.txt". For demand research, briefs, or Search Console monitoring use seo-program.

mblode/agent-skills · 77 tokens

ui-design

Designs and builds React/Next/Tailwind UI and audits visual and interaction defects. Use when asked to "build a landing page", "extract our design system", "add dark mode", "make this responsive", "remove UI slop", or "audit this component". For product decisions use product-design; for browser measurements use…

mblode/agent-skills · 80 tokens

pr-babysitter

Monitors or repairs an open GitHub PR: CI failures, conflicts, review threads, and merge readiness, reporting state changes. Use when asked to "watch this PR", "fix CI", "resolve conflicts", or "address review comments". For PR metadata use pr-creator; for npm release PRs use autoship.

mblode/agent-skills · 72 tokens

pr-reviewer

Reviews a diff or security scope read-only using evidence-tiered findings, structural and context-error rubrics, and repository review policy. Use when asked to "review my changes", "structural review", "review for AI patterns", or "security audit". For applying fixes use tidy; for UI defects use ui-design.

mblode/agent-skills · 68 tokens

autoship

Runs a changesets npm release through the version PR, CI publish, and registry verification. Use when asked to "release this package", "autoship", "merge Version Packages", or diagnose a release that did not publish. For feature PRs use pr-creator or pr-babysitter.

mblode/agent-skills · 63 tokens

readme-creator

Creates or rewrites a README for the project consumer, using verified install commands, a runnable quickstart, and house presentation conventions. Use when asked to "write a README", "rewrite our README", or replace scaffold boilerplate. For an in-place prose audit use docs-writing; for agent instructions use…

mblode/agent-skills · 68 tokens