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-governancegit 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-governance)<a href="https://agentmods.dev/skills/daymade/claude-code-skills/skill-governance"><img src="https://agentmods.dev/badge/skills/daymade/claude-code-skills/skill-governance.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.00129 | $0.01511 |
| Opus 5 | $0.00064 | $0.00756 |
| Sonnet 5 | $0.00026 | $0.00302 |
| Haiku 4.5 | $0.00013 | $0.00151 |
Grade D, and why
skill-governance scanned grade D with 2 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 4d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- exact-path `~/.codex/config.toml` policy for Codex discovery disables; Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
`rm -rf`. 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.
Skill Governance
Govern the Skill surface the user actually experiences: the intended hot or router entries are fully visible in a fresh host, cold capabilities remain reachable, editable behavior has one canonical owner, and every retirement is recoverable. A smaller directory count is not the outcome.
Required outcome contract
Before acting, state in one sentence:
- which entries or routers must be model-visible;
- which capabilities must remain available cold;
- which layer the user authorized changing;
- what fresh-host evidence will prove success.
If the request is only “how many / what is loaded / why”, stay read-only.
System model
Never collapse these layers into one:
- Canonical source — where owned behavior may be edited.
- Installed inventory — bundles and versions that exist on disk.
- Discovery policy — what Claude or Codex may discover.
- Model-visible catalog — metadata in a fresh model prompt.
- Runtime resources — hidden scripts, references, and assets a router still needs.
Installed does not mean active; active does not prove visible; visible does not prove usable. Counts and byte totals are diagnostic values only.
Authority order
Use current runtime truth, not remembered conventions:
- owned source repos and their manifests for editable Skill behavior;
claude plugin ... --jsonfor current Claude marketplace/install state;- the explicit source-sync activation manifest for managed Daymade links;
~/.agents/skillsas Codex's current user Skill root;- exact-path
~/.codex/config.tomlpolicy for Codex discovery disables; codex debug prompt-inputfor the actual fresh Codex catalog;- the installed vendor bundle for third-party cold resources.
~/.codex/skills is legacy/system compatibility unless a current local contract
explicitly assigns it another role. Never move third-party inventory into an
owned-source activation manifest just to make ownership look complete.
Route the request
What ships with it
5 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.
- 4d ago First seen · 163 lines · 129 tokens per session scan D d20649a3104c
skill-governance is a skill published in the GitHub repository daymade/claude-code-skills (1,381 stars, last pushed today), licensed MIT. It adds 129 tokens to every session and 1,511 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it D with 2 findings (reads agent configuration directories, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…