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.
git clone --depth 1 https://github.com/Amey-Thakur/AI-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/commands/amey-thakur/ai-skills/database-schema)<a href="https://agentmods.dev/commands/amey-thakur/ai-skills/database-schema"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/database-schema/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/commands/amey-thakur/ai-skills/database-schema"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/database-schema.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.00019 | $0.00399 |
| Opus 5 | $0.00010 | $0.00199 |
| Sonnet 5 | $0.00004 | $0.00080 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
database-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 9d 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.
What it actually says
You were invoked as a slash command. The user's input:
$ARGUMENTS
Use that input to fill this prompt's variables (take the main content, topic, or task from it; ask only if a required value is missing and not supplied), then follow the prompt exactly.
Design a database schema for: {requirements}
Database and context: {database}
Produce:
- The tables (or collections), each with columns, types, and a primary key. Model the entities and their relationships from the domain.
- The relationships: foreign keys and cardinality (one-to-many, many-to-many with a join table), with the referential-integrity constraints.
- Constraints that enforce correctness at the data layer: NOT NULL, UNIQUE, CHECK, defaults, enums. Let the database protect its own invariants.
- Indexes for the queries this schema will actually serve: index the columns used in WHERE, JOIN, and ORDER BY for the common access patterns (say what they are), and note the write cost so you do not over-index.
- The DDL (CREATE TABLE statements) for the chosen database, ready to run or adapt.
Rules: normalize to avoid update anomalies, then denormalize deliberately only where a real read pattern justifies it (say why). Design from the access patterns, not just the entities: the queries you must serve shape the indexes and sometimes the tables. Choose types precisely (right integer size, timestamp with time zone, decimal for money not float). For NoSQL, design around the access patterns first (single-table/denormalized as the store demands). Flag scale concerns (a column that will need partitioning, a hot table) and where requirements are ambiguous.
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.
- 9d ago First seen · 41 lines · 19 tokens per session scan A fbb7e4a4e475
database-schema is a command published in the GitHub repository Amey-Thakur/AI-SKILLS (7 stars, last pushed 6d ago), licensed MIT. It adds 19 tokens to every session and 399 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-09-03.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.