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/elct9620/ai-coding-skills/schemanpx skills add elct9620/ai-coding-skills --skill schemagit clone --depth 1 https://github.com/elct9620/ai-coding-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/elct9620/ai-coding-skills/schema)<a href="https://agentmods.dev/skills/elct9620/ai-coding-skills/schema"><img src="https://agentmods.dev/badge/skills/elct9620/ai-coding-skills/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.1 | $0.00073 | $0.01398 |
| Opus 5 | $0.00036 | $0.00699 |
| Sonnet 5 | $0.00015 | $0.00280 |
| Haiku 4.5 | $0.00007 | $0.00140 |
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 5d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Related Skills
- Designing the domain objects that the schema persists? → Use domain-modeling
- Schema change requires code restructuring? → Use refactoring
- Unsure which architectural layer the DTO belongs in? → Use architecture
Applicability Rubric
| Condition | Pass | Fail |
|---|---|---|
| Database structure change | Adding/modifying tables, columns, or indexes | No persistence changes |
| API contract work | Designing or changing request/response shapes | No API boundary changes |
| Data boundary crossing | Serialization/deserialization between layers | Data stays within single layer |
| Schema restructuring | Normalizing, denormalizing, or optimizing existing schemas | No structural changes needed |
Apply when: Any condition passes
Core Principles
Schema Design Principles
| Principle | Description | Violation Sign |
|---|---|---|
| Single Source of Truth | Each fact stored exactly once | Same data duplicated across tables without clear denormalization rationale |
| Explicit Contracts | Schemas defined clearly, with non-obvious values (status codes, control bytes, enum semantics) described inline at the boundary | Implicit structures, untyped fields, or values that require service code to interpret |
| Boundary Alignment | Schema matches system boundary responsibilities | Schema leaks internal details or couples unrelated concerns |
| Minimal Exposure | Expose only what consumers need | Internal fields visible in API responses, over-fetching by default |
Schema Types
| Type | Clean Architecture Layer | Purpose | Boundary with Domain Modeling |
|---|---|---|---|
| Database Schema | Infrastructure | Persist and query data efficiently | Translates domain entities into storage format |
| API Contract | Interface Adapters | Define external communication shape | Maps domain output to external representation |
| DTO | Interface Adapters | Transfer data between layers | Decouples domain model from transport format |
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.
- 5d ago First seen · 132 lines · 73 tokens per session scan A 72c9852aab24
schema is a skill published in the GitHub repository elct9620/ai-coding-skills (5 stars, last pushed 10d ago), licensed Apache-2.0. It adds 73 tokens to every session and 1,398 once invoked, about $0.0004 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
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.
debugging
How to debug tursodb using Bytecode comparison, logging, ThreadSanitizer, deterministic simulation, and corruption analysis tools.
sdk-design
Doctrine for designing and evolving any SDK Grida ships — TypeScript, Rust, or otherwise. "SDK" here means a surface that crosses a foreign-or-foreign-treated boundary: published packages, separately-versioned consumers, FFI bindings, public-by-design modules. An SDK's job is to refuse; a strict, honest surface…
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…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
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.