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 commands/christopherlouet/claude-base/data-modelinggit clone --depth 1 https://github.com/christopherlouet/claude-baseWhat 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.00000 | $0.00320 |
| Opus 5 | $0.00000 | $0.00160 |
| Sonnet 5 | $0.00000 | $0.00064 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
data-modeling 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.
What it actually says
Agent DATA-MODELING
Design and implement data models (schemas, ERD, data warehouse).
Request context
$ARGUMENTS
Objective
Design a data model suited to analytical or transactional use cases, with naming conventions, documentation and quality tests.
Workflow
- Understand the needs: analytical use cases, business entities, questions to answer, volume
- Choose the type of modeling (OLTP 3NF, Star Schema, Snowflake, Data Vault, Wide Table)
- Define the entities with relations and cardinality
- Apply naming conventions (fact_, dim_, _id, at, is, _amount)
- Implement with dbt if applicable (models, tests, YAML documentation)
- Manage Slowly Changing Dimensions (SCD Type 2) if needed
- Document with ERD (dbdiagram.io or draw.io) and data dictionary
- Add quality tests (unique, not_null, accepted_values)
Expected output
Data model with entities (type, description, estimated volume), ERD, data dictionary and example queries.
Related agents
| Agent | When to use it |
|---|---|
/data:data-pipeline |
Feed the model |
/growth:growth-analytics |
Analyze KPIs on the modeled data |
/ops:ops-database |
Optimize performance |
IMPORTANT: The model must answer business questions, not the other way around.
YOU MUST document every table and column.
NEVER create a model without understanding the use cases.
Think hard about the model's scalability and maintainability.
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 · 46 lines · 0 tokens per session scan A 166dd40a9078
data-modeling is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 320 tokens. 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 commands, from other repositories
cm
Stage working tree changes and create a Conventional Commit (no push).
address
Address code review feedback — corroborate, validate, and implement changes from a review's final.md.
post
Post the current OCR review to a GitHub PR.
show
Display a past OCR review session.
contract-version-bump
Classify and apply a version bump to a machine-readable contract (JSON Schema, API spec, config schema) — version literals, consumer compatibility, changelog entry, downstream drift.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.