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-migration-guardgit 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-migration-guard)<a href="https://agentmods.dev/skills/davila7/claude-with-skills/02-migration-guard"><img src="https://agentmods.dev/badge/skills/davila7/claude-with-skills/02-migration-guard/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-migration-guard"><img src="https://agentmods.dev/badge/skills/davila7/claude-with-skills/02-migration-guard.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.00023 | $0.00753 |
| Opus 5 | $0.00012 | $0.00377 |
| Sonnet 5 | $0.00005 | $0.00151 |
| Haiku 4.5 | $0.00002 | $0.00075 |
Grade A, and why
migration-guard 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 11d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migration review
Review the current migration file for naming conventions, rollback presence, and dangerous operations.
Step 1: Identify the file being reviewed
Use the current file context to determine which migration file is being worked on. If the user specified a file path, use that. If the context is ambiguous, ask the user which file to review before proceeding.
Step 2: Check the file name
Extract the file name (not the full path) and check it against two accepted naming formats:
Format A — Timestamp prefix:
Pattern: YYYYMMDDHHMMSS_description.sql
Example: 20260513143207_add_user_roles.sql
- Year: 4 digits
- Month: 2 digits (01–12)
- Day: 2 digits (01–31)
- Hour: 2 digits (00–23)
- Minute: 2 digits (00–59)
- Second: 2 digits (00–59)
- Underscore separator
- Description: lowercase letters, digits, underscores
- Extension:
.sql
Format B — Sequential prefix:
Pattern: NNNN_description.sql
Example: 0042_add_user_roles.sql
- Number: 1 or more digits, typically zero-padded to 4 digits
- Underscore separator
- Description: lowercase letters, digits, underscores
- Extension:
.sql
If the file name matches neither format, mark the naming check as FAIL and note the reason.
Step 3: Check for rollback
Read the file content and look for either:
- A clearly labeled rollback section (a comment like
-- rollback,-- down,-- revert, followed by SQL that undoes the migration) - A comment explicitly marking it as irreversible (e.g.,
-- This migration is irreversible,-- no rollback)
If neither is present, mark rollback as NO.
Step 4: Check for dangerous operations
Read the file and scan for these patterns (case-insensitive):
DROP TABLEwithoutIF EXISTSimmediately following — flag as WARNINGDROP TABLE IF EXISTS— acceptable, no warningDELETE FROMwithout aWHEREclause on the same or next line — flag as WARNINGUPDATEwithout aWHEREclause on the same or next line — flag as WARNINGTRUNCATEon any table — flag as WARNING (destructive, often irreversible in production)DROP COLUMN— flag as NOTICE (may break dependent code; not always dangerous but requires attention)
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.
- 11d ago First seen · 97 lines · 23 tokens per session scan A 694ab724e04f
migration-guard is a skill published in the GitHub repository davila7/claude-with-skills (12 stars, last pushed 3mo ago), licensed MIT. It adds 23 tokens to every session and 753 once invoked, about $0.0001 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…