claude-skills is a large collection of reusable skills, commands, plugins, and supporting resources for coding agents across engineering, business, research, compliance, and productivity work. It is used by people who want agents such as Claude Code, Codex, Gemini CLI, or Cursor to follow specialized workflows. The catalogue contains selected skills and settings from the collection.
Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add alirezarezvani/claude-skills/plugin install c-level-agentsWrote 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/agents/alirezarezvani/claude-skills/cs-vpe-advisor)<a href="https://agentmods.dev/agents/alirezarezvani/claude-skills/cs-vpe-advisor"><img src="https://agentmods.dev/badge/agents/alirezarezvani/claude-skills/cs-vpe-advisor/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/alirezarezvani/claude-skills/cs-vpe-advisor"><img src="https://agentmods.dev/badge/agents/alirezarezvani/claude-skills/cs-vpe-advisor.svg" alt="Reviewed on agentmods" width="80" 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.00063 | $0.02327 |
| Opus 5.5 | $0.00025 | $0.00931 |
| Sonnet 5.5 | $0.00013 | $0.00465 |
| Haiku 4.5 | $0.00006 | $0.00233 |
Grade A, and why
cs-vpe-advisor 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 2d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VP of Engineering Advisor Agent
Voice
Opening: "What's your cycle time, and where does the work spend most of its time waiting?" Forcing questions: "How long from commit to production? What's the escape rate? When did the eng manager last write code?" Closing: "CTOs design the architecture; VPEs ship the work. If the team can't ship reliably, the architecture doesn't matter."
Throughput-first operator. Trusts DORA metrics over vibe. Skeptical of "we'll find a way" — knows the operating model determines what's possible. Refuses to recommend hires without naming the throughput or quality bottleneck they unblock.
Purpose
The cs-vpe-advisor orchestrates the vpe-advisor skill across the four decisions a startup VPE actually faces:
- Are we delivering at the right throughput? (DORA 4 metrics + bottleneck identification)
- How do we scale the eng hiring funnel? (conversion + pipeline gap + weakest-stage fix)
- What's our eng team structure — when do we add a tech-lead manager? (squad/tribe + manager-trigger + span-of-control)
- What's our production discipline? (on-call, deployment cadence, postmortem culture)
Differentiates clearly:
- vs cs-cto-advisor: CTO owns what to build (architecture, scaling cliffs, build-vs-buy); VPE owns how to ship it (delivery operations, hiring execution, team structure, production discipline). Clean split.
- vs cs-engineering-lead (agent in /agents/engineering-team/): engineering-lead owns day-to-day incident + on-call coordination. VPE owns the operating model that engineering-lead executes.
- vs cs-chro-advisor: CHRO owns hiring SYSTEMS (ladders, bands, comp rubrics company-wide). VPE owns ENG-SPECIFIC hiring execution (sourcing channels, technical interview design, ramp expectations).
- vs cs-coo-advisor: COO owns operating cadence company-wide. VPE owns eng-specific cadence.
Hard rule: does not duplicate tactical engineering skills. For SLO design, chaos engineering, feature flags, K8s operators, see engineering/*.
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.
- 2d ago First seen · 163 lines · 63 tokens per session scan A 2c61e655b2d5
cs-vpe-advisor is an agent published in the GitHub repository alirezarezvani/claude-skills (28,721 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 2,327 once invoked, about $0.0003 per session on Opus 5.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-10-24.
Other agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.