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/tomaspozo/agentlink/databasenpx skills add tomaspozo/agentlink --skill databasegit clone --depth 1 https://github.com/tomaspozo/agentlinkWhat 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.00091 | $0.06959 |
| Opus 5 | $0.00046 | $0.03479 |
| Sonnet 5 | $0.00018 | $0.01392 |
| Haiku 4.5 | $0.00009 | $0.00696 |
Grade A, and why
database 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.
How it starts
The opening of the file, as written. The whole thing — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database
Schema files, migrations, and type generation. Architecture and core rules are in the builder agent.
Schema File Organization
supabase/database/
├── cluster/
│ └── extensions/ # one file per extension (cluster-level)
│ ├── pg_graphql.sql
│ ├── pg_net.sql
│ ├── pg_cron.sql
│ └── pgmq.sql
├── rbac/ # RBAC reference DATA (rows, not schema)
│ ├── roles.sql # synced by the RBAC reconcile, NOT by db apply
│ ├── permissions.sql
│ └── role_permissions.sql
├── config/ # role-level settings pg-delta can't model (imperative)
│ └── db_pre_request.sql # ALTER ROLE authenticator SET pgrst.db_pre_request
├── queue/ # pgmq queues — imperative, prod-safe, self-healing
│ └── agentlink_tasks.sql # DO $$ … pgmq.create('agentlink_tasks') … $$
├── cron/ # pg_cron jobs — imperative
│ └── process-stale-tasks.sql # fires the queue worker every minute
├── storage/ # buckets + storage.objects policies — imperative
│ └── avatars.sql
└── schemas/ # DECLARATIVE — applied by db apply / diffed into migrations
├── api/ # functions only — never create tables here
│ ├── schema.sql # CREATE SCHEMA api + grants / default privileges
│ └── functions/
│ ├── tenant_create.sql # one RPC per file
│ ├── profile_get.sql
│ └── chart_create.sql # custom api.chart_create
└── public/
├── schema.sql # public schema-level grants (e.g. supabase_auth_admin USAGE)
├── tables/
│ ├── profiles.sql # one table + its grants/RLS/indexes/triggers
│ ├── tenants.sql
│ └── charts.sql # custom entity table (example)
└── functions/
├── _auth_tenant_id.sql # one function per file
├── _internal_admin_handle_new_user.sql
└── _hook_before_user_created.sql
What ships with it
2 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.
- yesterday First seen · 299 lines · 91 tokens per session scan A 2bc183e3c190
database is a skill published in the GitHub repository tomaspozo/agentlink (6 stars, last pushed 1mo ago), licensed MIT. It adds 91 tokens to every session and 6,959 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…