OpenTag connects Slack with coding agents running on a computer controlled by the user, so channel mentions can queue work and return status, decisions, and evidence in the same thread. It is for engineering teams that want to run agents such as Claude Code, Codex, or Cursor against local checkouts through the Agent Client Protocol.
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 amplifthq/opentag --skill postgresql-planninggit clone --depth 1 https://github.com/amplifthq/opentagWrote 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/amplifthq/opentag/postgresql-planning)<a href="https://agentmods.dev/skills/amplifthq/opentag/postgresql-planning"><img src="https://agentmods.dev/badge/skills/amplifthq/opentag/postgresql-planning/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/amplifthq/opentag/postgresql-planning"><img src="https://agentmods.dev/badge/skills/amplifthq/opentag/postgresql-planning.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.00057 | $0.00953 |
| Opus 5.5 | $0.00023 | $0.00381 |
| Sonnet 5.5 | $0.00011 | $0.00191 |
| Haiku 4.5 | $0.00006 | $0.00095 |
Grade A, and why
postgresql-planning 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 2d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenMeld PostgreSQL Planning
All OpenMeld databases belong to the Amplift PlanetScale organization
(amplift), never the operator's personal organization. Pass --org amplift
explicitly; login defaults are not the resource owner.
The architecture is decided: Cloudflare Hyperdrive connects Workers to
PlanetScale PostgreSQL. Start from current source, not a new vendor comparison
or the superseded D1 capacity threshold. Production has used PostgreSQL since
the 2026-10-04 cutover. Shared staging reuses openmeld-postgresql-stg through
its own Hyperdrive binding and the guarded pnpm staging:deploy workflow.
The former staging D1 database is retained for historical test-data inspection.
Use standard PlanetScale Postgres for this foundation. Neki preview enrollment
does not change the chosen engine or authorize a sharded database migration.
The staging/local baseline is PostgreSQL 18 at the latest supported stable minor.
Use older versions only for a demonstrated compatibility constraint.
Production capacity changes require measured demand. Keep capacity stable while
isolating code-path regressions; use the current workflow's metrics and query
plans before recommending a larger machine.
Shortest useful start
- Read physical database ownership and the applicable section of the single PostgreSQL workflow.
- Run
pnpm pg planto see exact targets and migration checksums. Checktooling/postgresql/resources.json; a planned name is not a created resource. - Read the touched business owner's source, schema and contracts. Define who writes each fact and which readers need a transaction. Do not recreate RuntimeCoordinator authority, Space Durable Object state, or R2 file bodies.
- Implement in the existing owning package. Use standard PostgreSQL SQL and
the supported
pgdriver; do not build a D1 API emulator or a cross-database framework. Preserve externally visible IDs and shared schemas. - Run
pnpm pg:checkfor database infrastructure changes. For business work, add the smallest real PostgreSQL behavior checks for its failure boundary, then exercise affected consumers. Local infrastructure acceptance is not proof of cloud connectivity, production scale, or completed business migration.
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.
- 2d ago First seen · 77 lines · 57 tokens per session scan A d82663b2f00b
postgresql-planning is a skill published in the GitHub repository amplifthq/opentag (0 stars, last pushed 2d ago), licensed MIT. It adds 57 tokens to every session and 953 once invoked, about $0.0002 per session on Opus 5.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-10-15.
Other skills, from other repositories
engineer
Software engineer specialist (IRC handle @dev) dispatched to write and test application code, database schema migrations, and infrastructure configuration files.
azure-postgres-ts
Connect to Azure Database for PostgreSQL Flexible Server from Node.js/TypeScript using the pg (node-postgres) package. Use for PostgreSQL queries, connection pooling, transactions, and Microsoft Entra ID (passwordless) authentication. Triggers: "PostgreSQL", "postgres", "pg client", "node-postgres", "Azure PostgreSQL…
supabase
Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies…
butterbase
AI-native, open-source backend-as-a-service with a built-in Model Context Protocol server. Postgres, auth, storage, functions, AI gateway.
supabase-cli
This skill should be used when user asks to "use supabase CLI", "supabase init", "supabase start", "run migrations", "deploy edge functions", "manage Supabase project", or works with the supabase command-line tool for local development and project management.
supabase-js
This skill should be used when user asks to "use supabase-js", "query Supabase database", "supabase auth", "supabase storage", "supabase realtime", "supabase edge functions", or works with the @supabase/supabase-js JavaScript/TypeScript SDK.