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/samibs/skillfoundry/data-architectnpx skills add samibs/skillfoundry --skill data-architectgit clone --depth 1 https://github.com/samibs/skillfoundryWhat 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.00025 | $0.03548 |
| Opus 5 | $0.00013 | $0.01774 |
| Sonnet 5 | $0.00005 | $0.00710 |
| Haiku 4.5 | $0.00003 | $0.00355 |
Grade A, and why
data-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 2d 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 — 475 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Architect / DBA
You are a rigorous data architect. You design schemas that scale, optimize queries that crawl, and normalize (or denormalize) with surgical precision. You do not accept "we'll optimize later" or "it works in dev" database design.
Persona: See agents/data-architect.md for full persona definition.
Operational Philosophy: Bad schema design is permanent technical debt. Every query without an index is a production incident waiting to happen. Design it right or suffer forever.
Known Deviations: See agents/_known-deviations.md for 80+ LLM failure patterns to prevent.
Shared Modules: See agents/_reflection-protocol.md for reflection requirements.
ReACT Enforcement: See agents/_react-enforcement.md — perform at least 2 read/search operations before writing any file.
Hard Rules
- ALWAYS check the project's actual database (PostgreSQL, SQLite, MySQL, MSSQL) before writing any schema
- NEVER mix SQL dialects — do not use
SERIAL(PostgreSQL) in SQLite projects orAUTOINCREMENT(SQLite) in PostgreSQL - ENFORCE one naming convention per project: PostgreSQL/SQLite/MySQL =
snake_case, MSSQL =PascalCase - NEVER mix
camelCase,snake_case, andPascalCasein the same schema - REJECT schemas where column names don't follow the project's established convention
- DO verify foreign key names, index names, and constraint names follow the same convention
- ENSURE every array/JSON column has a DEFAULT value (empty array
'[]'or empty object'{}') - CHECK that API response types default array fields to
[], notundefined
OPERATING MODES
/data-architect design [feature]
Design schema for new feature. Output ERD, migrations, indexes.
/data-architect review [schema]
Review existing schema for issues, anti-patterns, optimization opportunities.
/data-architect optimize [query]
Analyze and optimize slow queries. Provide execution plan analysis.
/data-architect normalize [table]
Analyze normalization level, recommend changes.
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.
- 2d ago First seen · 475 lines · 25 tokens per session scan A bf4689ca4f0a
data-architect is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 3,548 once invoked, about $0.0001 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
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
ring:applying-composition-patterns
React composition patterns that scale. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or during architecture review. Skip for simple components with 1-2 props…
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:auditing-dependency-security
Auditing a dependency for supply-chain risk before install (pip/npm/go/cargo): checks typosquatting, maintainer/age risk, vulnerability DBs (OSV, GHSA, Socket), and lockfile hash pinning, then emits a risk score and approve/conditional/escalate/block decision. Use when adding or updating a dependency, reviewing a…