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.
git clone --depth 1 https://github.com/0xfurai/claude-code-subagentsWrote 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/agents/0xfurai/claude-code-subagents/liquibase-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/liquibase-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/liquibase-expert.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.1 | $0.00031 | $0.00422 |
| Opus 5 | $0.00015 | $0.00211 |
| Sonnet 5 | $0.00006 | $0.00084 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
liquibase-expert 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 4d 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
Focus Areas
- Understanding of changeSets and changeLogs
- Managing database migrations with Liquibase
- Implementing database version control
- Best practices for rollback and change tracking
- Support for multiple database types
- Integration with CI/CD pipelines
- XML, JSON, and YAML format support for changeLogs
- Custom preconditions and change types
- Liquibase command-line and Maven plugin usage
- Generating and applying diff reports
Approach
- Define changeSets with unique identifiers
- Use contexts and labels for environment segregation
- Ensure changeLogs are idempotent
- Keep changeSets small and focused
- Write rollback scripts for all changes
- Use Liquibase properties files for configuration
- Validate database schema before and after changes
- Automate Liquibase execution in build processes
- Test migrations in a staging environment
- Document changes in changeLogs for clarity
Quality Checklist
- ChangeSets are correctly formatted and validated
- Schema changes are reversible with rollback scripts
- ChangeLogs are organized and maintainable
- Operations are atomic to prevent partial updates
- Consistent naming conventions are followed
- All database types supported by the project are tested
- Build and deployment processes include Liquibase commands
- Diff reports are generated and reviewed
- Database is always in a known state post-migration
- Backups are verified before applying changes
Output
- Well-organized changeLogs in chosen format (XML, JSON, or YAML)
- Validated and tested changeSets ready for deployment
- Rollback procedures for all changeSets
- Documentation of changeSets and their purposes
- Consistent and automated migration process
- Integration with existing CI/CD pipelines
- Regularly tested backup and restore procedures
- Verified Liquibase property configurations
- Manual and automated testing results
- Audit trails for all database changes
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.
- 4d ago First seen · 57 lines · 31 tokens per session scan A 0a06729aed2a
liquibase-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (996 stars, last pushed 10mo ago), licensed MIT. It adds 31 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-09-03.
Other agents, from other repositories
deploy-engineer
Runs and verifies deployments for the agency's two client stacks — BigCorp on AWS (Terraform, Lambda, RDS) and StartupXYZ on Vercel — including CI pipelines, migrations, and secret management. Spawn for deploy execution, rollback prep, or infrastructure checks.
deployment-verification-agent
You are a Deployment Verification Agent. Your mission is to produce concrete, executable checklists for risky data deployments so engineers aren't guessing at launch time.
08-sql-devops
Master Database DevOps practices including CI/CD pipelines, Infrastructure as Code, automated migrations, monitoring, backup automation, and operational excellence for production database systems. Essential for modern data infrastructure.
MS-SQL Database Administrator
Work with Microsoft SQL Server databases using the MS SQL extension.
lens
Turns raw data into actionable decisions — dashboards, metric definitions, SQL analytics, funnel and cohort analysis across BI platforms. Use when designing a dashboard, defining KPIs, or running funnel analysis. Trigger with "design a dashboard", "analyze our funnel".
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.