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 loiane/specs-driven-development-spring-angular --skill flyway-or-liquibase-detectiongit clone --depth 1 https://github.com/loiane/specs-driven-development-spring-angularWrote 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/loiane/specs-driven-development-spring-angular/flyway-or-liquibase-detection)<a href="https://agentmods.dev/skills/loiane/specs-driven-development-spring-angular/flyway-or-liquibase-detection"><img src="https://agentmods.dev/badge/skills/loiane/specs-driven-development-spring-angular/flyway-or-liquibase-detection/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/loiane/specs-driven-development-spring-angular/flyway-or-liquibase-detection"><img src="https://agentmods.dev/badge/skills/loiane/specs-driven-development-spring-angular/flyway-or-liquibase-detection.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.00035 | $0.00836 |
| Opus 5 | $0.00017 | $0.00418 |
| Sonnet 5 | $0.00007 | $0.00167 |
| Haiku 4.5 | $0.00003 | $0.00084 |
Grade A, and why
flyway-or-liquibase-detection 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 9d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flyway or Liquibase detection
Detection
.github/scripts/detect-stack.sh reports one of:
flyway—flyway-coreinpom.xmlANDsrc/main/resources/db/migration/exists.liquibase—liquibase-coreinpom.xmlANDsrc/main/resources/db/changelog/exists.none— neither.both— fatal. Refuse to proceed; ask the user to remove one.
Record the result in 03-design.md under ### Inputs from detect-stack.sh.
Flyway conventions
- File path:
src/main/resources/db/migration/V{version}__{description}.sql - Versioning:
V1__init.sql,V2__add_gift_card_table.sql,V3__add_index_gift_card_code.sql - One migration per logical change. Never edit a checked-in migration; add a new one.
- Repeatable migrations (views, functions):
R__view_active_orders.sql. - Forward-only by default. If a migration is destructive, the design must include a
## Rollbacksection in03-design.md.
-- V12__add_gift_card_table.sql
CREATE TABLE gift_card (
id UUID PRIMARY KEY,
code VARCHAR(64) NOT NULL UNIQUE,
balance NUMERIC(12,2) NOT NULL CHECK (balance >= 0),
created_at TIMESTAMPTZ NOT NULL DEFAULT now()
);
CREATE INDEX ix_gift_card_code ON gift_card(code);
Liquibase conventions
- Master changelog:
src/main/resources/db/changelog/db.changelog-master.yaml - Per-feature changeset file:
db/changelog/changes/2026-04-18-gift-card.yaml - Include via
<include file="changes/2026-04-18-gift-card.yaml"/>. - Each changeset has
id,author, and is immutable once merged.
databaseChangeLog:
- changeSet:
id: gift-card-1
author: spring-implementer
changes:
- createTable:
tableName: gift_card
columns:
- column: { name: id, type: UUID, constraints: { primaryKey: true } }
- column: { name: code, type: VARCHAR(64), constraints: { nullable: false, unique: true } }
- column: { name: balance, type: NUMERIC(12,2), constraints: { nullable: false } }
- column: { name: created_at, type: TIMESTAMPTZ, defaultValueComputed: now() }
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.
- 9d ago First seen · 79 lines · 0 tokens per session scan A a3cd5aae9bf8
flyway-or-liquibase-detection is a skill published in the GitHub repository loiane/specs-driven-development-spring-angular (59 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 836 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
spec-kitty-mission-review
Review a fully merged Spec Kitty mission post-merge (all WPs done/approved) to verify spec→code fidelity, FR coverage, drift, risks, and security. Triggers: "review the merged mission", "post-merge mission review", "verify the completed mission", "audit the mission implementation", "mission-level acceptance review"…
spec-kitty-mission-system
Understand how Spec Kitty missions work: the 4 built-in mission types, how they define workflows via step contracts and action indices, how missions and work packages relate, how templates are resolved through the 6-tier chain, and how doctrine artifacts (procedures, tactics, directives) compose mission behavior.…
spec-kitty-runtime-next
Drive the canonical spec-kitty next --mission control loop for mission advancement. Load agent profiles at init, apply action-scoped doctrine context at each step boundary, and pull specific tactics/directives on demand. Triggers: "run the next step", "what should runtime do next", "advance the mission", "what is the…
spec-kitty-git-workflow
Understand how Spec Kitty manages git: what git operations Python handles automatically, what agents must do manually, worktree lifecycle, auto-commit behavior, merge execution, and the safe-commit pattern. Triggers: "how does spec-kitty use git", "worktree management", "auto-commit", "who commits what", "git…
spec-kitty-spdd-reasons
Drive REASONS Canvas authoring and review for Spec Kitty missions that opted in to Structured-Prompt-Driven Development (SPDD) via charter selection. Triggers: "use SPDD", "use REASONS", "generate a REASONS canvas", "apply structured prompt driven development", "make this mission SPDD". Does NOT handle: enforcing SPDD…
spec-kitty-runtime-review
Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only…