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 app-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/app-evolver)<a href="https://agentmods.dev/skills/daymade/claude-code-skills/app-evolver"><img src="https://agentmods.dev/badge/skills/daymade/claude-code-skills/app-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/app-evolver"><img src="https://agentmods.dev/badge/skills/daymade/claude-code-skills/app-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.00083 | $0.01677 |
| Opus 5.5 | $0.00033 | $0.00671 |
| Sonnet 5.5 | $0.00017 | $0.00335 |
| Haiku 4.5 | $0.00008 | $0.00168 |
Grade A, and why
app-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 5d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App Evolver
Improve the application's actual user result. Extract transferable mechanisms, resolve their fit with the current product, implement authorized improvements, and verify them through the application's consuming surface.
Use this as an orchestration Skill. Keep repository engineering, research,
history access and release operations with their existing owners. For a Skill
target use skill-evolver; for competitor intelligence alone use
competitors-analysis; for a new product specification use the available
requirements workflow. Do not replace those owners with another execution engine.
1. Bind the application and unfinished result
Before research or edits, establish:
- Exact application, repository/ref, platform and runtime or deployment identity.
- Original user request, current product contract and active stage; distinguish long-term positioning from the work selected now.
- User-visible improvement, falsifiable acceptance evidence, authorized deliverables, protected behavior/data and stopping condition.
- Analysis-only versus implementation authorization, and any unresolved product choice whose answer changes the outcome.
Reuse earlier user decisions; ask in the current conversation only for missing information or a real unresolved choice. Use the host's question tool when available. State the evidence, alternatives, consequences and recommendation. Do not delegate a user decision through another agent.
For multiple applications, bind each contract and acceptance path separately. A successful design, permission or measurement in one app is an unverified proposal in another. Do not transfer a desktop contract to its mobile sibling without checking the sibling's current contract.
Read repository instructions and relevant domain Skills. Pin the code used for judgment to an immutable ref; inspect current runtime/config separately. Preserve other writers' work and coordinate overlapping ownership before editing. On resume, reconcile the latest request, actual artifacts and unfinished evidence; continue from the first unmet result rather than replaying the original plan.
What ships with it
4 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.
- 5d ago Changed · +15 lines · +8 tokens per session 4bf9437175e1
- 6d ago First seen · 150 lines · 75 tokens per session scan A 5c79dff8662a
app-evolver is a skill published in the GitHub repository daymade/claude-code-skills (1,473 stars, last pushed today), licensed MIT. It adds 83 tokens to every session and 1,677 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-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.