comp-analysis

comp-analysis is a skill for Claude Code from anthropics/knowledge-work-plugins. It costs 51 tokens per session (798 once invoked), scanned A, original, Apache-2.0.

A compensation analysis for comparing pay with market data, placing people in salary bands and modelling equity grants.

In plain words
What is it for?
Benchmarking a role, reviewing uploaded compensation data and modelling salary, bonus, benefits or stock-based packages.
Why use it?
It helps identify pay outliers, assess whether an offer is competitive and understand how changes to equity affect compensation.

Skill for Claude Code ✓ vendor

Written for Claude Code: argument-hint in frontmatter.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md)..

Part of the human-resources plugin — 9 skills shipped together

Good fit Benchmarking a role, reviewing uploaded compensation data and modelling salary, bonus, benefits…

Compare 6 skills from other repositories ↓
About the project

Knowledge Work Plugins is an open-source collection of Claude extensions organized around roles such as productivity, sales, and customer support. Each plugin combines role-specific guidance, connectors, commands, and sub-agents so knowledge workers can use Claude with their team’s tools and processes. The catalogue entries are examples of, or workflows from, this plugin collection.

anthropics/knowledge-work-plugins · 23,902 stars · on GitHub

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/anthropics/knowledge-work-plugins
agentmods
npx agentmods add skills/anthropics/knowledge-work-plugins/comp-analysis

Made for: Claude Code.

Or install human-resources, the plugin that ships this one along with the rest of its 9 skills.

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 comp-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/anthropics/knowledge-work-plugins/comp-analysis.svg)](https://agentmods.dev/skills/anthropics/knowledge-work-plugins/comp-analysis)
Your own site
<a href="https://agentmods.dev/skills/anthropics/knowledge-work-plugins/comp-analysis"><img src="https://agentmods.dev/badge/skills/anthropics/knowledge-work-plugins/comp-analysis.svg" alt="Measured on agentmods" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 798 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.00051 $0.00798
Opus 5 $0.00026 $0.00399
Sonnet 5 $0.00010 $0.00160
Haiku 4.5 $0.00005 $0.00080

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

Security

Grade A, and why

comp-analysis 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 3d 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

2 near-identical copies found in the catalogue:

human-resources/skills/comp-analysis/SKILL.md · 93 lines

How it starts

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

/comp-analysis

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Analyze compensation data for benchmarking, band placement, and planning. Helps benchmark compensation against market data for hiring, retention, and equity planning.

Usage

/comp-analysis $ARGUMENTS

What I Need From You

Option A: Single role analysis "What should we pay a Senior Software Engineer in SF?"

Option B: Upload comp data Upload a CSV or paste your comp bands. I'll analyze placement, identify outliers, and compare to market.

Option C: Equity modeling "Model a refresh grant of 10K shares over 4 years at a $50 stock price."

Compensation Framework

Components of Total Compensation

  • Base salary: Cash compensation
  • Equity: RSUs, stock options, or other equity
  • Bonus: Annual target bonus, signing bonus
  • Benefits: Health, retirement, perks (harder to quantify)

Key Variables

  • Role: Function and specialization
  • Level: IC levels, management levels
  • Location: Geographic pay adjustments
  • Company stage: Startup vs. growth vs. public
  • Industry: Tech vs. finance vs. healthcare

Data Sources

  • With ~~compensation data: Pull verified benchmarks
  • Without: Use web research, public salary data, and user-provided context
  • Always note data freshness and source limitations

Output

Provide percentile bands (25th, 50th, 75th, 90th) for base, equity, and total comp. Include location adjustments and company-stage context.

## Compensation Analysis: [Role/Scope]

### Market Benchmarks
| Percentile | Base | Equity | Total Comp |
|------------|------|--------|------------|
| 25th | $[X] | $[X] | $[X] |
| 50th | $[X] | $[X] | $[X] |
| 75th | $[X] | $[X] | $[X] |
| 90th | $[X] | $[X] | $[X] |

**Sources:** [Web research, compensation data tools, or user-provided data]

### Band Analysis (if data provided)
| Employee | Current Base | Band Min | Band Mid | Band Max | Position |
|----------|-------------|----------|----------|----------|----------|
| [Name] | $[X] | $[X] | $[X] | $[X] | [Below/At/Above] |

### Recommendations
- [Specific compensation recommendations]
- [Equity considerations]
- [Retention risks if applicable]

Read the full file on GitHub · 93 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. 3d ago First seen · 93 lines · 51 tokens per session scan A 1af196cd1c38

Subscribe to this mod's changes

comp-analysis is a skill published in the GitHub repository anthropics/knowledge-work-plugins (23,902 stars, last pushed yesterday), licensed Apache-2.0. It adds 51 tokens to every session and 798 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-09-03.

Related

Other skills, from other repositories