Borrowing it
Nothing to install: this file belongs to MattModeCode/claude-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/MattModeCode/claude-skills/main/CLAUDE.mdgit clone --depth 1 https://github.com/MattModeCode/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/instructions/mattmodecode/claude-skills/claude-md)<a href="https://agentmods.dev/instructions/mattmodecode/claude-skills/claude-md"><img src="https://agentmods.dev/badge/instructions/mattmodecode/claude-skills/claude-md.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.00826 | $0.00826 |
| Opus 5 | $0.00413 | $0.00413 |
| Sonnet 5 | $0.00165 | $0.00165 |
| Haiku 4.5 | $0.00083 | $0.00083 |
Grade A, and why
claude-skills CLAUDE.md 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for Claude Code when working in this repo.
This is a personal library of published Claude Code skills. One folder per skill lives under
skills/. The job here is to keep every skill documented the same way, so the repo stays
consistent as it grows.
Repo layout
README.md # generic library index — NEVER holds skill-specific detail
CLAUDE.md # this file
LICENSE
skills/
<skill-name>/
SKILL.md # the skill itself: frontmatter (name, description) + body
README.md # human documentation for that skill
SKILL.mdis what Claude Code loads and runs. Itsdescription:frontmatter drives auto-triggering — leave it alone when you're only writing docs; it's tuned separately.README.md(per skill) is the human-facing page someone reads when they browse into the folder. Skill-specific detail lives here, never in the root README.- Root
README.mdis the index for the whole library and stays generic.
When adding a new skill
Do all of these, in order:
-
Create
skills/<skill-name>/containing theSKILL.md. -
Write
skills/<skill-name>/README.mdusing the template below. -
Add one row to the Skills Library table in the root
README.md(name links to the folder, Docs links to the skill's README):| [`<skill-name>`](./skills/<skill-name>) | <one line: what it does> | [README](./skills/<skill-name>/README.md) | -
Keep the root README generic. If a skill needs a dependency, the root README mentions it only as "some skills require X" — exact requirements go in the skill's own README.
-
Update the GitHub About description only if the library's overall framing changes — not per skill.
-
Make the change on a branch and open a PR; don't push docs straight to
main.
Per-skill README.md template
Common skeleton for every skill, then a type-specific body.
# <skill-name>
<One-line summary.> <When it auto-triggers — Claude loads it on a matching request; you
don't name it.>
## Requirements
- **[Claude Code](https://claude.com/claude-code)**.
- <Any hard dependency, e.g. gstack — note if the skill is non-functional without it.>
## Usage
<Concrete invocation examples / inputs.>
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 · 85 lines · 826 tokens per session scan A 2678ebdf75d3
claude-skills CLAUDE.md is an instructions file published in the GitHub repository MattModeCode/claude-skills (1 stars, last pushed 1mo ago), licensed MIT. It adds 826 tokens to every session, about $0.0041 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-31.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.