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 skills/motlin/claude-code-plugins/liquibase-lock-resolvernpx 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.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.00063 | $0.00339 |
| Opus 5 | $0.00032 | $0.00169 |
| Sonnet 5 | $0.00013 | $0.00068 |
| 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 yesterday.
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 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.
- yesterday 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 (15 stars, last pushed today), licensed Apache-2.0. It adds 63 tokens to every session and 339 once invoked, about $0.0003 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-09-04.
Other skills, from other repositories
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.
debugging
How to debug tursodb using Bytecode comparison, logging, ThreadSanitizer, deterministic simulation, and corruption analysis tools.
sdk-design
Doctrine for designing and evolving any SDK Grida ships — TypeScript, Rust, or otherwise. "SDK" here means a surface that crosses a foreign-or-foreign-treated boundary: published packages, separately-versioned consumers, FFI bindings, public-by-design modules. An SDK's job is to refuse; a strict, honest surface…
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.