Claude Code Skills Marketplace is a collection and marketplace of skills, plugins, agents, and instructions that extend Claude Code with specialized development workflows. It is for developers who want to install existing workflows or create, validate, and package their own Claude Code skills.
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 daymade/claude-code-skills --skill skill-evolvergit clone --depth 1 https://github.com/daymade/claude-code-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/skills/daymade/claude-code-skills/skill-evolver)<a href="https://agentmods.dev/skills/daymade/claude-code-skills/skill-evolver"><img src="https://agentmods.dev/badge/skills/daymade/claude-code-skills/skill-evolver/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/skills/daymade/claude-code-skills/skill-evolver"><img src="https://agentmods.dev/badge/skills/daymade/claude-code-skills/skill-evolver.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.00056 | $0.01987 |
| Opus 5.5 | $0.00022 | $0.00795 |
| Sonnet 5.5 | $0.00011 | $0.00397 |
| Haiku 4.5 | $0.00006 | $0.00199 |
Grade A, and why
skill-evolver 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 6d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daymade Skill Evolver
Orchestrate a research-driven improvement round for a named existing Skill through the current specialist Skills. Keep the original result, stage inputs, dependencies and returned evidence bound together. An unchanged Skill is a valid outcome when the evidence supports keeping it.
Keep orchestration here; execute specialist work through its current owner. Skill Creator makes and validates selected changes; it does not choose this round's business goal or research plan. When the request is diagnosis-only, remain read-only.
Resolve the target and result
Resolve the named Skill to its authoritative repository or project source, current release identity, and actual loaded entry when relevant. Read its entry and the resources used by the affected jobs. Distinguish source, installed copies and host consumption; do not edit a cache as if it were the owner.
State the user-visible result, the observation that could disprove it, supported jobs to preserve, authorized deliverables, and stopping condition before selecting improvements. Include the original reported failure. Do not replace it with a research report, a shorter prompt, a score, or green checks. Ask only for missing information or a user-owned choice that changes the work; reuse existing answers and authorization.
Keep the outcome criterion stable while comparing candidates. Correct a proxy against the original requirement before accepting an improvement; do not move the goal to whichever output the candidate already produces.
Gather evidence that can change a decision
Start with current implementation, project decisions, existing tools/Skills, provided examples, and previously verified work. Reuse evidence whose source and conditions still apply under the current owner's contract. Before executing a selected stage, load stage handoffs and follow its applicable owner route; this reference specifies inputs and returned results, not a second specialist procedure.
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.
- 6d ago First seen · 184 lines · 56 tokens per session scan A 1a5fb0cf09ea
skill-evolver is a skill published in the GitHub repository daymade/claude-code-skills (1,473 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 1,987 once invoked, about $0.0002 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-12.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.