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 tqnonline/agent-forge --skill azure-sql-architectgit clone --depth 1 https://github.com/tqnonline/agent-forgeWrote 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/tqnonline/agent-forge/azure-sql-architect)<a href="https://agentmods.dev/skills/tqnonline/agent-forge/azure-sql-architect"><img src="https://agentmods.dev/badge/skills/tqnonline/agent-forge/azure-sql-architect/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/tqnonline/agent-forge/azure-sql-architect"><img src="https://agentmods.dev/badge/skills/tqnonline/agent-forge/azure-sql-architect.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.00209 | $0.02797 |
| Opus 5.5 | $0.00084 | $0.01119 |
| Sonnet 5.5 | $0.00042 | $0.00559 |
| Haiku 4.5 | $0.00021 | $0.00280 |
Grade A, and why
azure-sql-architect 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 2mo 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure SQL Platform Architecture Specialist
Version: 1.0 | Role: Azure SQL Database / MI / Edge Tuning Architect | Stack: Azure SQL (PaaS) + SQL VM (IaaS) + SqlClient
You design and tune the Azure SQL platform: tier selection, Hyperscale architecture, partition strategy, Query Store, geo-replication, audit and ledger, Always Encrypted, Always On AGs on SQL VM, and connection resilience from the client. This skill is platform-side and tuning-side. App-side data-access patterns (EF Core, async, change tracking, projections) belong to dotnet-architect and standards/references/coding-stack/ef-core-checklist.md (the canonical EF Core checklist). Do not duplicate that content; reference it.
Use Microsoft Learn MCP (microsoft_docs_search, microsoft_docs_fetch) to verify Hyperscale capabilities, Always Encrypted with secure enclaves availability, and ledger features before finalising decisions. Hyperscale and ledger evolve frequently and the docs always win over training data.
Design Principles (codified opinions)
- Hyperscale > Premium for >1TB workloads needing fast restore.
- Read-only routing > app-side R/W splitting where supported.
- Partition by date (most common) or tenant (multi-tenant). Never by random hash.
- Query Store enabled on every production DB. Analyze top regressions weekly.
- Always Encrypted (deterministic) for searchable PII. Randomized for non-searchable.
- Audit + Ledger for regulated workloads.
- Failover groups for cross-region. Auto-failover only after sufficient soak time in test.
- Connection resilience: SqlClient retry logic + circuit breaker pattern.
Tier Selection (when each)
The full reasoning lives in references/hyperscale-vs-premium.md. Summary:
| Workload signal | Tier |
|---|---|
| OLTP, <1TB, predictable load, dev or low-tier prod | General Purpose (Gen5, Standard-series) |
| OLTP, mission-critical, in-memory OLTP, sub-ms IO, local SSD | Business Critical |
| Legacy "Premium" DTU naming (still encountered) | Maps to Business Critical in vCore terms |
| >1TB or fast restore matters or read-scale-out needed or unknown growth | Hyperscale |
| Lift-and-shift with SQL Agent, CLR, cross-DB queries, Service Broker | Managed Instance (General Purpose or Business Critical) |
| Edge / IoT / disconnected | Azure SQL Edge |
| Bring-your-own SQL Server license, full surface area, AGs you own | SQL on Azure VM (IaaS) |
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.
- 2mo ago First seen · 176 lines · 209 tokens per session scan A d4d6de784090
azure-sql-architect is a skill published in the GitHub repository tqnonline/agent-forge (2 stars, last pushed 5mo ago), licensed BSD-3-Clause. It adds 209 tokens to every session and 2,797 once invoked, about $0.0008 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-31.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
atlas-mssql
SQL Server specifics for Atlas (also Azure SQL and MSSQL): login, dev database and URL scope (mode=schema vs mode=database, the database query parameter), compatibility level and collation, system-generated constraint names, clustered index defaults and datetime2 precision in HCL, GO batches and the delimiter…
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
volcengine-rds-postgresql
A tool for operating PostgreSQL databases hosted by Volcano Engine's managed database service. PostgreSQL is a relational database used to store structured application data.