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 fusengine/agents --skill astro-dbgit clone --depth 1 https://github.com/fusengine/agentsWrote 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/fusengine/agents/astro-db)<a href="https://agentmods.dev/skills/fusengine/agents/astro-db"><img src="https://agentmods.dev/badge/skills/fusengine/agents/astro-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/fusengine/agents/astro-db"><img src="https://agentmods.dev/badge/skills/fusengine/agents/astro-db.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.01228 |
| Opus 5.5 | $0.00012 | $0.00491 |
| Sonnet 5.5 | $0.00006 | $0.00246 |
| Haiku 4.5 | $0.00003 | $0.00123 |
Grade A, and why
astro-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 21d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Also covers integration with Astro Actions for end-to-end type-safe form-to-database flows. @astrojs/db is deprecated on npm (last release v0.21.3, June 2026) and listed as Removed in the official Astro v7 upgrade guide — for new projects this skill recommends Drizzle, Kysely, node:sqlite, or a direct libSQL client instead; existing Astro 6 projects must migrate off it before upgrading to Astro 7.
Astro DB
Type-safe SQL database built into Astro, powered by libSQL/Turso. Use for structured data without external backend services.
⚠️ Removal notice:
@astrojs/dbis deprecated on npm ("Use a database client (Drizzle, Kysely, etc.) directly instead"; last release v0.21.3) and the official Astro v7 upgrade guide lists it under "Removed" — remove it from dependencies when upgrading. Replacements: Node's built-innode:sqlite(Node adapter), Drizzle directly, Kysely, or a libSQL/Turso client. The content below documents the legacy Astro 6 API for maintaining/migrating existing projects.
Agent Workflow (MANDATORY)
Before ANY implementation, spawn 3 agents in parallel, one Agent call each with a name:
- fuse-ai-pilot:explore-codebase - Check existing db/config.ts, tables, and Actions
- fuse-ai-pilot:research-expert - Verify Astro DB API via Context7/Exa
- mcp__context7__query-docs - Check Astro 6 DB docs for column types and CRUD
After implementation, run fuse-ai-pilot:sniper for validation.
Overview
When to Use
- Storing structured data (comments, users, posts, forms)
- Building full-stack Astro apps without external DB setup
- Combining with Astro Actions for type-safe form handling
- Deploying to production with Turso (libSQL cloud)
- Seeding development data for local testing
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.
- 21d ago Changed bc3a0fc5452a
- 1mo ago Changed 2ac84bcab4c0
- 1mo ago First seen · 104 lines · 29 tokens per session scan A 3cd51558d32c
astro-db is a skill published in the GitHub repository fusengine/agents (32 stars, last pushed 6d ago), licensed MIT. It adds 29 tokens to every session and 1,228 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
tiledbvcf
Stores and retrieves genomic variant calls with TileDB-VCF. Use for indexed single-sample VCF/BCF ingestion, incremental cohorts, region and sample queries, streaming results, allele statistics, QC, and VCF/BCF export locally or through TileDB Cloud.
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.
constraint-debug
Compatibility alias for the Elixir/Phoenix plugin's Ecto constraint debugger. Invoke explicitly with /ecto:constraint-debug.
n1-check
Compatibility alias for the Elixir/Phoenix plugin's N+1 query checker. Invoke explicitly with /ecto:n1-check.
ts-db-perf
Optimize TypeScript code that interacts with databases. Use this skill when the user wants to fix N+1 queries, add caching, improve transaction safety, prevent race conditions, simplify async flows, or generally speed up a TypeScript backend. Triggers on phrases like "optimize", "slow query", "N+1", "race condition"…