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 motlin/claude-code-plugins --skill liquibase-lock-resolvergit clone --depth 1 https://github.com/motlin/claude-code-pluginsWrote 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/motlin/claude-code-plugins/liquibase-lock-resolver)<a href="https://agentmods.dev/skills/motlin/claude-code-plugins/liquibase-lock-resolver"><img src="https://agentmods.dev/badge/skills/motlin/claude-code-plugins/liquibase-lock-resolver/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/motlin/claude-code-plugins/liquibase-lock-resolver"><img src="https://agentmods.dev/badge/skills/motlin/claude-code-plugins/liquibase-lock-resolver.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.00063 | $0.00343 |
| Opus 5.5 | $0.00025 | $0.00137 |
| Sonnet 5.5 | $0.00013 | $0.00069 |
| Haiku 4.5 | $0.00006 | $0.00034 |
Grade A, and why
liquibase-lock-resolver 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 22d 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
Resolve Liquibase Test Locks
Follow the java:maven-cli skill whenever invoking Maven.
Confirm the failure
Inspect the failing output and confirm a Liquibase lock signature. Do not delete files for an unrelated database, migration, or connectivity failure.
Determine the narrowest Maven module and test command that reproduces the failure.
Find disposable H2 files
Search recursively for H2 files only beneath Maven target/ directories. Typical names end in .mv.db, .trace.db, .lock.db, or .db.
Review the exact paths before deletion. Exclude source trees, checked-in fixtures, databases outside target/, and unrelated build artifacts.
Remove the stale databases
Delete only the reviewed H2 paths, using the environment's safe file-removal facility when available. Report every removed file. Do not remove an entire target/ directory unless the user separately asks for a clean build.
Verify the resolution
Rerun the narrowest affected Maven test with the current module's upstream dependencies included when necessary. Do not use offline mode.
If no H2 files exist or the lock recurs, investigate instead of broadening deletion. Check for a still-running test JVM, concurrent builds sharing a database path, a non-H2 JDBC URL, or cleanup missing from the test lifecycle. Report the remaining cause and safe next action.
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.
- 22d ago Changed bbadd4679002
- 1mo ago First seen · 31 lines · 63 tokens per session scan A 024125bf486c
liquibase-lock-resolver is a skill published in the GitHub repository motlin/claude-code-plugins (20 stars, last pushed yesterday), licensed Apache-2.0. It adds 63 tokens to every session and 343 once invoked, about $0.0003 per session on Opus 5.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-09-04.
Other skills, from other repositories
reproduce-bug
Reproduce a reported bug in googleapis/mcp-toolbox and decide whether it is real, delivering an evidence-backed verdict: confirmed, already fixed, misconfiguration, client-side, works as intended, not reproducible, or blocked. Use whenever a maintainer asks you to reproduce, verify, confirm, or investigate a bug…
triage-issues
Triage GitHub issues in the googleapis/mcp-toolbox repo: propose the correct labels (type / priority / product / status), check for duplicates, verify a bug has enough info to act on, and draft a triage comment. Use whenever a maintainer asks you to triage, label, categorize, prioritize, or "look at" an issue (or a…
postgresql-indexing
PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing…
graphjin-eval
Create, extend, run, baseline, and diagnose GraphJin agent evaluations through the graphjin eval CLI.
axiom-audit-grdb-performance
Use when the user mentions GRDB performance review, slow GRDB queries, app-group database setup audit, a ValueObservation that stopped updating, or pre-release GRDB scan.
django-perf-review
Django performance code review. Use when asked to "review Django performance", "find N+1 queries", "optimize Django", "check queryset performance", "database performance", "Django ORM issues", or audit Django code for performance problems.