Claude With Skills is a progressive course that teaches developers to create reusable, portable Agent Skills for Claude Code, from basic SKILL.md files to advanced automation and plugin packaging. It is intended for developers who want repeatable instructions and workflows instead of repeatedly pasting the same guidance. The catalogue contains the course's skills, agents, and instruction.
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 davila7/claude-with-skills --skill 02-headlessgit clone --depth 1 https://github.com/davila7/claude-with-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/davila7/claude-with-skills/02-headless)<a href="https://agentmods.dev/skills/davila7/claude-with-skills/02-headless"><img src="https://agentmods.dev/badge/skills/davila7/claude-with-skills/02-headless/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/davila7/claude-with-skills/02-headless"><img src="https://agentmods.dev/badge/skills/davila7/claude-with-skills/02-headless.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.00045 | $0.00422 |
| Opus 5 | $0.00023 | $0.00211 |
| Sonnet 5 | $0.00009 | $0.00084 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
summarize-changes-headless 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 12d 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.
What it actually says
Current changes
!git diff HEAD
Instructions
If the diff above is empty, output exactly: No uncommitted changes.
Otherwise, output the summary in the following format with no surrounding prose:
SUMMARY
- [bullet point describing the first logical change]
- [bullet point describing the second logical change]
[continue as needed, two to five bullets maximum]
RISKS
- [risk] or NONE
Rules for the SUMMARY section:
- Each bullet describes a logical change, not a file change. If three files were modified to implement one feature, that is one bullet.
- Use present tense: "Add validation for email field" not "Added" or "Adding".
- Maximum 80 characters per bullet.
Rules for the RISKS section:
- List only genuine risks: missing error handling, hardcoded credentials, removed tests, breaking API changes.
- If there are no risks, write NONE on a single line.
- Do not list stylistic observations as risks.
Output nothing else. No preamble, no "Here is the summary:", no closing remarks. The output must be parseable by a script that splits on the SUMMARY and RISKS headers.
Note: this skill is optimized for headless use with claude -p "/summarize-changes-headless". The concise, structured output can be captured with claude -p "/summarize-changes-headless" > summary.txt and processed by downstream tools. Compare this to the interactive summarize-changes skill, which produces more readable prose suited to an interactive session. In headless mode, conciseness and consistent structure matter more than readability, because there is no follow-up turn to ask for clarification or a reformatted response.
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.
- 12d ago First seen · 42 lines · 45 tokens per session scan A 05d37a97b287
summarize-changes-headless is a skill published in the GitHub repository davila7/claude-with-skills (12 stars, last pushed 4mo ago), licensed MIT. It adds 45 tokens to every session and 422 once invoked, about $0.0002 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 skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…