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 gusbavia/fabric-apps-skills --skill fabric-app-sqldb-writebackgit clone --depth 1 https://github.com/gusbavia/fabric-apps-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/gusbavia/fabric-apps-skills/fabric-app-sqldb-writeback)<a href="https://agentmods.dev/skills/gusbavia/fabric-apps-skills/fabric-app-sqldb-writeback"><img src="https://agentmods.dev/badge/skills/gusbavia/fabric-apps-skills/fabric-app-sqldb-writeback/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/gusbavia/fabric-apps-skills/fabric-app-sqldb-writeback"><img src="https://agentmods.dev/badge/skills/gusbavia/fabric-apps-skills/fabric-app-sqldb-writeback.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.00150 | $0.01799 |
| Opus 5 | $0.00075 | $0.00899 |
| Sonnet 5 | $0.00030 | $0.00360 |
| Haiku 4.5 | $0.00015 | $0.00180 |
Grade A, and why
fabric-app-sqldb-writeback 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fabric App · SQL DB Write-back
The architecture for Fabric Apps that write: the app owns its SQL Database (a managed child of the App item), a small job mirrors Lakehouse Gold into it, and write-back entities live alongside the mirrors. One database, one SDK, instant read-your-own-writes.
Lakehouse (canonical, untouched)
↓ copy job (~30s, headless via SP over TDS)
App SQL Database
├─ mirror entities (DimX, FactY...) ← refreshed by re-running the job
└─ write-back entities (Comment, Edit…) ← transactional, instant
↓ ONE SDK (RayfinClient)
SPA — every read and write
Why not write to the Lakehouse directly (the scars)
- Its SQL endpoint is read-only — the GraphQL over it has no mutations.
- Its sync is lazy — a write landed in OneLake in seconds and surfaced through the API a day later. Users will not wait a day to see their own comment.
- Two sources = two auth flows + dual-source merge logic + optimistic-cache band-aids in the frontend, forever.
The copy job moves that complexity out of the frontend into one script. Microsoft's name for this serving pattern: operational data store.
Step 1 · Model entities (TypeScript decorators)
Mirror entities for the Gold tables the app reads + the app's own write-back entities. Keep mirror columns text-friendly (no enum constraints — source data will surprise you). Register everything in the schema the client SDK is typed against.
// rayfin/data/DimCustomer.ts — a mirror entity, minimal shape
@entity()
export class DimCustomer {
@field({ type: "uuid", primaryKey: true }) id!: string;
@field({ type: "text", unique: true }) customer_id!: string;
@field({ type: "text" }) customer_name!: string;
@field({ type: "text", optional: true }) segment?: string;
}
// register it in rayfin/data/schema.ts so the client SDK is typed
Schema apply is OWNER-ONLY: npx rayfin up db apply needs one interactive login by the item owner. The SP cannot apply schema (403 "Only AppBackend artifact owner") — but handles everything else headless.
What ships with it
1 file 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.
- 11d ago First seen · 117 lines · 150 tokens per session scan A 743aefb2229f
fabric-app-sqldb-writeback is a skill published in the GitHub repository gusbavia/fabric-apps-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 150 tokens to every session and 1,799 once invoked, about $0.0007 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
payload
Use when working with Payload projects (payload.config.ts, collections, fields, hooks, access control, Payload API). Use when debugging validation errors, security issues, relationship queries, transactions, or hook behavior.
nornicdb-bolt-client
Drive NornicDB from a Bolt client (neo4j-go-driver/v5 or any other Neo4j Bolt driver). Use when classifying retryable vs permanent errors, sizing UNWIND/MERGE batch writes, configuring connection defaults, or implementing retry logic against NornicDB. NornicDB speaks the same wire as Neo4j 5; this skill calls out the…
nornicdb-grpc
Drive NornicDB over gRPC — the Qdrant-compatible surface (Collections, Points, Snapshots) plus the additive NornicSearch service. Use when ingesting via Qdrant SDKs, migrating from Qdrant, or running hybrid text+vector search from a non-Bolt client. Covers connection, RPC catalog, collection→database mapping…
nornicdb-neo4j-migration
Migrate from Neo4j 5 to NornicDB end-to-end over Bolt. Covers schema replication (constraints + indexes including fulltext and vector), node and edge replication using hot-path UNWIND/MERGE shapes from the cookbook, label preservation strategy, what does and does not transfer, the cutover playbook. Points to runnable…
pydantic-resolve-3step
A three-stage development method for Python projects built with pydantic-resolve, starting with agreed data models and ending with application interfaces. It uses an ER diagram, which shows database entities and their relationships, plus ORM models that represent database records in code.
webiny-api-opensearch-catalog
Name: createOpenSearchClient Import: import { createOpenSearchClient } from "webiny/api/opensearch" Source: @webiny/api-opensearch/client.ts.