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/bhanu91221/sfdx-iq/data-modelgit clone --depth 1 https://github.com/bhanu91221/sfdx-iqWrote 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/bhanu91221/sfdx-iq/data-model)<a href="https://agentmods.dev/commands/bhanu91221/sfdx-iq/data-model"><img src="https://agentmods.dev/badge/commands/bhanu91221/sfdx-iq/data-model.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.00009 | $0.01230 |
| Opus 5 | $0.00005 | $0.00615 |
| Sonnet 5 | $0.00002 | $0.00246 |
| Haiku 4.5 | $0.00001 | $0.00123 |
Grade A, and why
data-model 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 3d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/data-model
Analyze an existing Salesforce data model or design a new one. For existing models: map relationships, identify data skew, and find missing indexes. For new designs: plan objects, relationships, record types, and external IDs.
Workflow
-
Determine mode
- Ask the user: analyze existing data model or design a new one
- If analyzing: identify scope — specific objects or entire org
- If designing: gather business requirements
- Delegate to the solution-designer agent for domain-specific analysis
-
Mode: Analyze existing data model
a. Inventory objects
- Scan
force-app/main/default/objects/for custom object definitions - For connected orgs, query
EntityDefinitionfor standard and custom objects in use - For each object, record: API name, label, record count estimate, sharing model
b. Map relationships
- Identify all lookup and master-detail relationships
- Build a relationship graph showing parent-child connections
- Identify junction objects (objects with two master-detail relationships)
- Map polymorphic lookups (e.g.,
WhatId,WhoId) - Calculate relationship depth: how many levels of parent-child nesting exist
c. Identify data skew risks
- Flag lookup fields where a single parent has an excessive number of child records
- Common skew patterns: Account with millions of child records, single user as owner of many records
- Check for record locking risks due to parent-child relationships
- Identify objects with potential large data volumes (over 1M estimated records)
d. Check indexing and selectivity
- Identify custom fields marked as external IDs (automatically indexed)
- Review SOQL queries in Apex for WHERE clause fields
- Flag frequently queried fields that are not indexed or external IDs
- Check for queries that would trigger full table scans
e. Detect design issues
- Objects with too many custom fields (approaching 800 limit)
- Deep relationship hierarchies (more than 5 levels)
- Missing validation rules on required business fields
- Inconsistent naming conventions across objects and fields
- Missing descriptions on objects and fields
- Record types without corresponding page layouts
- Scan
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.
- 3d ago First seen · 124 lines · 9 tokens per session scan A 74135a4e9d1a
data-model is a command published in the GitHub repository bhanu91221/sfdx-iq (2 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 1,230 once invoked, about $0.0000 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 commands, from other repositories
notebook-query
Query the notebook knowledge base (SQLite) built by /agy:notebook — precise, grounded, cited. Ask in natural language ("sum the amounts by category", "which docs mention 'Acme Corp'", "build a project timeline") or pass raw SQL. Read-only. Use this when you need exact aggregates/lookups across a document corpus…
database-setup
Use when a project needs to store data and has no database yet. Setting up Supabase, creating tables, writing queries, and connecting them to the frontend. Written for designers.
ingest
Manually add knowledge to the Weaviate store.
integrate
/forge:integrate is the integration assistant for connecting your project to external services. It covers version control (GitHub, GitLab), monitoring (Sentry, Datadog), communication (Slack, Discord), databases (PostgreSQL, Redis, MongoDB), and cloud platforms (AWS, GCP, Vercel, Netlify). For each service, it checks…
db-reviewer
Reviews Postgres/Supabase schema, migrations, queries, and RLS for safety and performance. Use when DB code changes, before applying a migration, or inside /...
symfony-migrations
Create and manage Doctrine migrations for database schema changes.