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 dublyo/saas-skills --skill dublyobase-backend-buildergit clone --depth 1 https://github.com/dublyo/saas-skillsWrote 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/dublyo/saas-skills/dublyobase-backend-builder)<a href="https://agentmods.dev/skills/dublyo/saas-skills/dublyobase-backend-builder"><img src="https://agentmods.dev/badge/skills/dublyo/saas-skills/dublyobase-backend-builder/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/dublyo/saas-skills/dublyobase-backend-builder"><img src="https://agentmods.dev/badge/skills/dublyo/saas-skills/dublyobase-backend-builder.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.00115 | $0.08434 |
| Opus 5 | $0.00057 | $0.04217 |
| Sonnet 5 | $0.00023 | $0.01687 |
| Haiku 4.5 | $0.00012 | $0.00843 |
Grade A, and why
dublyobase-backend-builder 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 11d 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 — 1,031 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dublyobase Backend Builder
Use this skill to turn an app brief into a working Dublyobase backend. Dublyobase is a Postgres-backed PocketBase/Supabase-style backend with projects, collections, records CRUD, app auth, sessions, files, SMTP, S3-compatible storage, cron jobs, backups, schema import, realtime SSE, webhooks, request logs, quotas, app organizations, invitations, and remote HTTP MCP.
This skill is written for AI agents. It favors direct, verified backend creation over long planning. Keep changes conservative, verify every critical workflow, and never expose secrets.
Inputs
Require these before changing a live instance:
DUBLYOBASE_URL: base URL, for examplehttps://example.com.- Either
DUBLYOBASE_MCP_TOKENforPOST /mcp, or an admin bearer token for/admin/api/*. - Target project slug, or permission to create one.
- App brief: users, workflows, tenants, roles, data, permissions, files, automations, email needs, frontend origins, and sample records.
If URL or credentials are missing, ask for them. If the app brief is enough to infer a conservative schema, do not ask extra questions.
Never print full tokens, API keys, SMTP passwords, S3 secrets, database URLs, restore files, or private webhook secrets in the final answer. Mask them.
Operating Rules
- Inspect capabilities first:
GET /health,GET /ready, MCPinitialize, and MCPtools/list. - Treat
tools/listas the source of truth for MCP. Some product features may only be available through admin REST. - Prefer project-scoped MCP tokens for app-specific schema/data work.
- Use admin MCP or admin REST only for instance-level settings: SMTP, storage, admin CORS, full backups/restores, MCP tokens, and super admins.
- Make destructive operations opt-in: collection deletion, field drops, destructive schema import, restore mode, global CORS wildcard, and full-instance backup changes.
- Use dry runs where available before schema import or restore.
- Preserve existing user data. Prefer additive schema changes unless the user asked for migration or cleanup.
- Verify with real REST requests after MCP writes. A schema that exists but cannot be used from the public API is not complete.
- Final reports must include project slug, created resources, API examples, verification evidence, and remaining boundaries.
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.
- 11d ago First seen · 1,031 lines · 115 tokens per session scan A 74fc98aa7478
dublyobase-backend-builder is a skill published in the GitHub repository dublyo/saas-skills (10 stars, last pushed 2mo ago), licensed MIT. It adds 115 tokens to every session and 8,434 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
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…
butterbase
AI-native, open-source backend-as-a-service with a built-in Model Context Protocol server. Postgres, auth, storage, functions, AI gateway.
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…
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.
supabase-node
Express/Hono with Supabase and Drizzle ORM.