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 projectgit 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/project)<a href="https://agentmods.dev/skills/davila7/claude-with-skills/project"><img src="https://agentmods.dev/badge/skills/davila7/claude-with-skills/project/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/project"><img src="https://agentmods.dev/badge/skills/davila7/claude-with-skills/project.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.00040 | $0.00388 |
| Opus 5 | $0.00020 | $0.00194 |
| Sonnet 5 | $0.00008 | $0.00078 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
project-conventions 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 10d 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
Instructions
This skill is installed at the project scope. Its expected location on disk is:
.claude/skills/project-conventions/SKILL.md
(That path is relative to the root of the repository.)
Tell the user this is a demonstration of a project-scoped skill, then list the following made-up conventions to show how project-specific knowledge can be encoded in a skill:
Example project conventions (demonstration only)
Branching
- Feature branches:
feat/<ticket-id>-short-description - Bugfix branches:
fix/<ticket-id>-short-description - All PRs must target
main. Never merge directly tomainlocally.
Commit messages
- Conventional Commits format:
type(scope): description - Allowed types: feat, fix, docs, style, refactor, test, chore
- Reference the Linear ticket ID in the commit body when applicable
Code style
- TypeScript strict mode is enabled. Do not use
anywithout a comment explaining why. - All exported functions must have JSDoc comments.
- No
console.login production code — use the internal logger atsrc/lib/logger.ts.
Testing
- Unit tests live alongside source files:
foo.ts/foo.test.ts - Integration tests live in
tests/integration/ - Minimum coverage threshold: 80% lines. CI will fail below this.
After listing the conventions, remind the user that this skill would normally contain real conventions for the actual project, committed to version control so that all developers on the team get the same guidance when working with Claude Code.
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.
- 10d ago First seen · 42 lines · 40 tokens per session scan A 85558b7d47f0
project-conventions is a skill published in the GitHub repository davila7/claude-with-skills (11 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 388 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
gsd-quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
gsd-quick-batch
Batch several /gsd:quick-shaped tasks together — planned, dispatched, and merged as one run.
gh-issues
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5]…
gsd-pause-work
Create context handoff when pausing work mid-phase.
gsd-ship
Create PR, run review, and prepare for merge after verification passes.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.