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 gul-labs/craftsman-marketplace --skill craft-dbgit clone --depth 1 https://github.com/gul-labs/craftsman-marketplaceWrote 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/gul-labs/craftsman-marketplace/craft-db)<a href="https://agentmods.dev/skills/gul-labs/craftsman-marketplace/craft-db"><img src="https://agentmods.dev/badge/skills/gul-labs/craftsman-marketplace/craft-db/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/gul-labs/craftsman-marketplace/craft-db"><img src="https://agentmods.dev/badge/skills/gul-labs/craftsman-marketplace/craft-db.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.00118 | $0.02294 |
| Opus 5 | $0.00059 | $0.01147 |
| Sonnet 5 | $0.00024 | $0.00459 |
| Haiku 4.5 | $0.00012 | $0.00229 |
Grade A, and why
craft-db 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 12d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DB Craft
This skill encodes one engineer's standard for database work, applied the same way across every repo. The method and opinions live here; the specifics (which ORM, which dialect, which migration tool, what the tenant-scope helper is called) live in the target repo — always discover them first, never assume or hardcode.
Operating principle — discover before you build
Different repos are at different points in their DB evolution. Before touching anything, spend a few minutes mapping what already exists so you extend rather than duplicate or fight the grain:
package.json/ lockfile → isdrizzle-orm,prisma,knex,pg,mysql2, or similar already present?- Existing migration directory (e.g.
drizzle/,prisma/migrations/,db/migrations/) → what conventions are already established (naming, timestamps, reversibility)? - Schema files → column naming style (camelCase vs snake_case), timestamp columns (
createdAt/created_at), soft-delete column name and type, how tenant id is stored and named. - Query helpers → is there a shared conditions/helpers file that enforces tenant scoping and soft-delete filters? Read it before writing any query.
- Dialect → Postgres, MySQL, SQLite? Some patterns (advisory locks,
RETURNING, expression indexes) are dialect-specific.
State what you found, then propose the smallest set of changes that achieves the goal.
The data layers (work in this order)
-
Schema design — model the domain correctly before writing a line of migration code. Choose the right types, enforce NOT NULL where the domain demands it, express relationships as real foreign keys, and name columns consistently with the existing schema. See
references/schema.md. -
Migrations — translate the schema design into a forward-only migration, reviewed before it ever runs. Prefer reversible migrations where the cost is low (drop → add back); know when forward-only is the honest choice. See
references/migrations.md.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 158 lines · 118 tokens per session scan A 8602e96fe6be
craft-db is a skill published in the GitHub repository gul-labs/craftsman-marketplace (1 stars, last pushed today), licensed MIT. It adds 118 tokens to every session and 2,294 once invoked, about $0.0006 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-31.
Other skills, from other repositories
ggsql
Write ggsql queries — a grammar of graphics for SQL. Use when the user wants to create, modify, or understand a ggsql visualization query.
ecto-patterns
Ecto patterns — schemas, changesets, queries, migrations, Multi, associations, preloads, upserts. Use when editing Repo calls, Ecto.Query, or schema fields. Skip for Ash.
phoenix-contexts
Phoenix context design — creating/splitting contexts, Scope (1.8+), Ecto.Multi, PubSub, routers, plugs, controllers. Use when editing contexts, routers, or designing boundaries.
ecto-n1-check
Detect N+1 query anti-patterns specifically — Repo calls inside Enum/for loops, missing preloads on associations. Use when N+1 is explicitly suspected, NOT for unrelated Ecto questions or wider database performance.
data-migration
Moves data from one system to another without losing it or corrupting it — profiling the source before mapping, deciding between big-bang and parallel-run cutover, reconciling counts and values rather than assuming, handling the records that will not map cleanly, and planning a rollback that is actually executable.…
data-modeling
Designs the warehouse and semantic layer — source-to-mart structure, dimensional modeling, grain, slowly changing dimensions, and the metric layer analytics reads through. Use this to design or restructure a warehouse, model a new source, decide on grain or table structure, build a semantic or metric layer, or…