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 agentmods add instructions/schwepps/skills/claude-mdgit clone --depth 1 https://github.com/schwepps/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/schwepps/skills/claude-md)<a href="https://agentmods.dev/instructions/schwepps/skills/claude-md"><img src="https://agentmods.dev/badge/instructions/schwepps/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 | $0.00925 | $0.00925 |
| Opus 5 | $0.00463 | $0.00463 |
| Sonnet 5 | $0.00185 | $0.00185 |
| Haiku 4.5 | $0.00093 | $0.00093 |
Grade A, and why
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 3d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
This is a Claude Code skills marketplace repository containing documentation-based skills that extend Claude Code with specialized workflows. Skills are pure markdown - no build system, dependencies, or executable code.
Project Structure
skills/
├── .claude-plugin/
│ ├── marketplace.json # Full marketplace (all skills)
│ ├── marketplace-seo.json # SEO skills only
│ └── marketplace-music.json # Music skills only
├── scripts/
│ └── build-skills.sh # Build script for packaging
├── dist/ # Generated packages (after build)
├── skill-name/
│ ├── SKILL.md # Required: Main skill definition
│ └── references/ # Optional: Supporting documentation
│ └── *.md files
└── CLAUDE.md
Creating a New Skill
1. Create Skill Directory
mkdir -p skill-name/references
touch skill-name/SKILL.md
2. SKILL.md Frontmatter
---
name: skill-name
description: This skill should be used when the user asks to "specific phrase 1", "specific phrase 2", or "specific phrase 3". Be concrete about trigger conditions.
license: MIT
metadata:
author: Schwepps
version: "1.0.0"
category: marketing|music|development|etc
tags: tag1, tag2, tag3
---
Critical: The description field determines when Claude activates the skill:
- Use third-person phrasing: "This skill should be used when..."
- Include exact phrases users would say to trigger it
- Be specific and concrete, not vague
3. SKILL.md Content Structure
After frontmatter, include:
- When to Use: Clear activation criteria
- Workflow/Methodology: Phased approach with specific steps
- Output Format: Template showing expected deliverable structure
- Scoring Guide (for audits): Quantitative evaluation criteria
- Quick Version: Abbreviated workflow for rapid execution
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.
- 3d ago First seen · 125 lines · 925 tokens per session scan A 232ee00b45f6
skills CLAUDE.md is an instructions file published in the GitHub repository schwepps/skills (16 stars, last pushed 7mo ago), licensed MIT. It adds 925 tokens to every session, about $0.0046 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 instructions, from other repositories
ai-workflow AGENTS.md
Instructions for cunhaax/ai-workflow, covering ai workflow template, rules — non-negotiable, project overview, commands and architecture.
trackly-cli CLAUDE.md
Claude Code instructions for trackly-app/trackly-cli, covering trackly-cli, tech stack, backend production source of truth, directory structure and key commands.
com-example-config-AsyncTestConfig
Instructions for PIsberg/vibetags, covering copilot instructions for asynctestconfig and immutable type.
pupila CLAUDE.md
Instructions for FranRom/pupila, covering claude.md, where things live, stack, run locally and repo layout.
claude-bridge AGENTS.md
Instructions for kadaba/claude-bridge, covering agents.md — using claude-bridge from any ai coding cli, two independent channels, 1. coordination (the conversation), 2. file transfer (the bytes) — same for every tool and workflows.
McpServer AGENTS.md
AGENTS.md instructions for sharpninja/McpServer, covering agent instructions, session start, rules, byrd test gate and where things live.