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
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.
git clone --depth 1 https://github.com/alirezarezvani/claude-skillsWrote 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/commands/alirezarezvani/claude-skills/cp)<a href="https://agentmods.dev/commands/alirezarezvani/claude-skills/cp"><img src="https://agentmods.dev/badge/commands/alirezarezvani/claude-skills/cp.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.00014 | $0.00210 |
| Opus 5 | $0.00007 | $0.00105 |
| Sonnet 5 | $0.00003 | $0.00042 |
| Haiku 4.5 | $0.00001 | $0.00021 |
Grade A, and why
cp 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.
What it actually says
- Run
/reviewto ensure lint/tests/security checks pass locally. - Review and stage changes with
git add(avoid staging generated or secret files). - Craft a Conventional Commit message (types: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert).
- Use
.github/commit-template.txtand include Context / Testing / Reviewers blocks. - Never add AI attribution strings to commits.
- Use
- Commit with
git commitusing the prepared message. If commitlint fails, fix the message and retry. - Push to origin:
git push origin $(git branch --show-current). - Trigger remote checks for visibility:
gh workflow run ci-quality-gate.yml --ref $(git branch --show-current)
- Wait for workflow to finish (
gh run watch --workflow ci-quality-gate.yml) before opening a pull request.
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 · 15 lines · 14 tokens per session scan A 64b771123934
cp is a command published in the GitHub repository alirezarezvani/claude-skills (25,635 stars, last pushed 8d ago), licensed MIT. It adds 14 tokens to every session and 210 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-30.
Other commands, from other repositories
atomic-commits
Analyze staged changes and organize them into intuitive atomic commits following conventional commits.
validate-pr-description
Use when validating a PR title and description for conventional commit format, issue linking keywords, and template compliance before submission.
ops-hotfix
Command "ops-hotfix" from christopherlouet/claude-base, covering hotfix agent, request context, objective, workflow and expected output.
work-commit-push-pr
Pointer: Claude Code ships a native /commit-push-pr that owns the commit + push + PR macro. This command adds the foundation's pre-flight gate and convention sources on top — it does not re-implement the macro.
work-commit
Prepare and perform a clean commit following conventions.
work-flow-feature
Complete workflow for developing a new feature, from exploration to merge.