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 agentmods add skills/qauth-labs/qauth/schemanpx skills add qauth-labs/qauth --skill schemagit clone --depth 1 https://github.com/qauth-labs/qauthWrote 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/qauth-labs/qauth/schema)<a href="https://agentmods.dev/skills/qauth-labs/qauth/schema"><img src="https://agentmods.dev/badge/skills/qauth-labs/qauth/schema.svg" alt="Measured on agentmods" 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 | $0.00050 | $0.02272 |
| Opus 5 | $0.00025 | $0.01136 |
| Sonnet 5 | $0.00010 | $0.00454 |
| Haiku 4.5 | $0.00005 | $0.00227 |
Grade A, and why
schema 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 4d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Schema Rules
You are working with the QAuth database layer. This document reflects the
CURRENT shipped schema: the identifier-abstraction model (ADR-002,
implemented via Epic #224, PRs #225–#230, migrations 0009–0011). users
is a pure identity anchor; authentication methods live in user_credentials;
identity data lives in user_attributes. The legacy monolithic columns
(users.email/email_normalized/password_hash) were dropped in migration
0011 and no longer exist.
Identity Model (CURRENT — shipped)
Three tables (see libs/infra/db/src/lib/schema/core.ts + identity.ts):
users— identity anchor ONLY:id(uuidv7 PK — the stable OIDCsub),realm_id,enabled,first_name/last_name(→ OIDCnameclaim),metadata, timestamps,last_login_at. (The vestigialemail_verified/email_verified_atcolumns were dropped in #261, migration 0012; verified state lives incredential_data/user_attributes.)user_credentials— one row per authentication method per user.provider_type('password' | 'wallet' | 'oidc_*', plain text — no enum),external_sub(normalized email for password; DID/upstream sub later),credential_datajsonb (for'password':{ password_hash, email_verified }snake_case — shape owned bypasswordCredentialDataSchemain@qauth-labs/server-federation). UNIQUE(realm_id, provider_type, external_sub)— since #230 this is the sole duplicate-registration guard.user_attributes— claims as data:(user_id, source, attr_key)UNIQUE,attr_value,verified, optionalexpires_at. Trust order (wallet > oidc_* > self_reported) is app-code policy (selectTrustedAttribute), not a DB constraint.
Login lookup (password auth)
SELECT * FROM user_credentials
WHERE realm_id = $realm_id
AND provider_type = 'password'
AND external_sub = $normalized_email
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.
- 4d ago First seen · 159 lines · 50 tokens per session scan A ff644d764a72
schema is a skill published in the GitHub repository qauth-labs/qauth (24 stars, last pushed 8d ago), licensed Apache-2.0. It adds 50 tokens to every session and 2,272 once invoked, about $0.0003 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-30.
Other skills, from other repositories
saas-builder
Clone, verify, map, and build on top of ixartz/SaaS-Boilerplate for a user's SaaS idea. Use when a user wants to reuse SaaS Boilerplate, evaluate how their product fits it, or build product-specific pages, database schema, roles, permissions, MVP features, and launch scope on top of the boilerplate.
write-e2e-test
Write end-to-end (e2e) tests for authgear-server. Use when the user asks to write, add, or create e2e tests. The tests live in e2e/tests/ and are YAML-driven.
add-portal-screen
Add screens or components to the portal frontend. Use when the user asks to create a new portal page, screen, tab, or UI component.
api-design
Review or design APIs for Authgear. In review mode, evaluates a design draft against the checklist. In ideation mode, develops a design from a description and self-reviews it.
update-deps
Audit and fix dependency vulnerabilities in Go and Node.js packages. Runs govulncheck for Go and npm audit for each package.json directory. Commits fixes directory by directory.
new-siteadmin-api
Full pipeline for adding a new Site Admin API feature — from OpenAPI spec through implementation plan to working service. Use when adding a new endpoint or filling in real data for an existing stub.