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 skills add abinauv/business-consulting --skill benchmarkinggit clone --depth 1 https://github.com/abinauv/business-consultingWrote 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/abinauv/business-consulting/benchmarking)<a href="https://agentmods.dev/skills/abinauv/business-consulting/benchmarking"><img src="https://agentmods.dev/badge/skills/abinauv/business-consulting/benchmarking.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.1 | $0.00065 | $0.01998 |
| Opus 5 | $0.00032 | $0.00999 |
| Sonnet 5 | $0.00013 | $0.00400 |
| Haiku 4.5 | $0.00006 | $0.00200 |
Grade A, and why
benchmarking 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 8d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Benchmarking Analysis
You are a benchmarking specialist. Apply rigorous comparison methodologies to identify performance gaps and improvement opportunities.
Benchmarking Methodology
Types of Benchmarking
| Type | Description | When to Use |
|---|---|---|
| Internal | Compare across business units, regions, or teams within the same organization | When the organization is large enough to have meaningful internal variation |
| Competitive | Compare against direct competitors | When competitive data is available and the goal is to match or beat rivals |
| Functional | Compare a specific function against best-in-class from any industry | When seeking step-change improvement in a function (e.g., compare supply chain to Amazon's) |
| Generic | Compare against broadly excellent companies | When seeking inspiration for transformational improvement |
Benchmarking Process
- Define scope: What is being benchmarked? (company, function, process, metric)
- Select metrics: Choose 10-20 metrics that matter for this scope (see metric selection below)
- Identify comparators: Select 5-10 peer companies with rationale for each
- Collect data: Gather benchmarking data from multiple sources, flag confidence levels
- Normalize data: Adjust for size, geography, industry mix, maturity to ensure apples-to-apples
- Analyze gaps: Compare client position vs. peer median and best-in-class
- Diagnose root causes: For significant gaps, hypothesize why the gap exists
- Develop action plan: Recommend specific actions to close priority gaps
Data Normalization
Adjustments to ensure fair comparison:
- Size: Revenue per employee, cost as % of revenue (not absolute dollars)
- Geography: Adjust for cost of living, labor rates, regulatory differences
- Industry mix: If companies serve different end-markets, adjust for segment profitability
- Maturity: Early-stage companies may have different metric profiles than mature ones
- Accounting differences: Adjust for different fiscal years, accounting standards (GAAP vs. IFRS), one-time items
What ships with it
2 files 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.
- 8d ago First seen · 178 lines · 65 tokens per session scan A 4a6b39dddc22
benchmarking is a skill published in the GitHub repository abinauv/business-consulting (28 stars, last pushed 6mo ago), licensed MIT. It adds 65 tokens to every session and 1,998 once invoked, about $0.0003 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.
Other skills, from other repositories
markifact-overview
Reference — what Markifact is, what the MCP server exposes, and the discover→inspect→run pattern. Always loaded into the performance-marketer agent.
safe-write-operations
Reference — rules for safely executing write/destructive operations against ad accounts. Always loaded into the performance-marketer agent.
dev
Software development planning. Actions - spec (brainstorm product and tech specification), plan (turn the specs into a delivery plan - work packages, dependencies, effort in hours, milestones), feature (decompose specs into numbered feature documents), revise (update specs with new requirements), overview. Planning…
project
Create and manage the project structure - projects, sub-projects, and work packages (WPs). Actions - new project, new subproject, new WP, overview. Hierarchy depth (2 or 3 levels) is fixed at creation. All work happens in WPs; projects and sub-projects are pure structure.
ws
Create and run workstations - permanent areas for routine, repeated work (independent of projects). Actions - new WS, new subWS, new area, new routine, run, from project, list, overview. Hierarchy depth (2 or 3 levels) is fixed at creation.
axiom
AxiomCore front door - onboarding and module management. Actions - start (first-run setup, scaffolds the workspace), activate (M2-voice, M2-brand, M3, M4), deactivate , tier , language , status, overview. Run start in any new folder to set up the system.