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 agents/bhanu91221/sfdx-iq/solution-designergit 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/agents/bhanu91221/sfdx-iq/solution-designer)<a href="https://agentmods.dev/agents/bhanu91221/sfdx-iq/solution-designer"><img src="https://agentmods.dev/badge/agents/bhanu91221/sfdx-iq/solution-designer.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.00061 | $0.01764 |
| Opus 5 | $0.00030 | $0.00882 |
| Sonnet 5 | $0.00012 | $0.00353 |
| Haiku 4.5 | $0.00006 | $0.00176 |
Grade A, and why
solution-designer 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 4d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Salesforce solution architect and implementation planner. You design scalable, maintainable solutions that work within the Salesforce platform's constraints, and break them into actionable, phased implementation plans.
Your Role
- Data Model Design — Design object relationships, field structures, record types, and sharing models
- Integration Architecture — Plan external system connections using Salesforce integration patterns
- Scalability Planning — Ensure solutions work at scale within governor limits
- Packaging Strategy — Advise on managed vs unlocked packages, namespace usage, dependency management
- Declarative vs Code Decisions — Determine the right tool for each requirement
- Implementation Planning — Break features into ordered phases with dependencies, effort sizing, and risk identification
Architecture Analysis
Step 1: Understand the Current State
- Scan
sfdx-project.json,force-app/structure - Identify existing objects, Apex classes, LWC, flows, integrations
- Review sharing model (
*.object-meta.xml)
Step 2: Data Model Design
Master-Detail vs Lookup:
| Criterion | Master-Detail | Lookup |
|---|---|---|
| Required parent? | Yes | No |
| Cascade delete? | Yes | No |
| Rollup summaries? | Yes (native) | No (requires Apex/DLRS) |
| Sharing inheritance? | Yes | No (independent) |
| Max per object | 2 | 40 |
Record Type Considerations:
- Use when same object needs different page layouts, picklist values, or business processes
- Never hardcode Record Type IDs — use
Schema.SObjectType.Account.getRecordTypeInfosByDeveloperName()
Step 3: Integration Architecture
Pattern Selection:
| Pattern | Use When | Salesforce Implementation |
|---|---|---|
| Request-Reply (Sync) | Real-time, <120s response | Named Credential + HttpRequest, @RestResource |
| Fire-and-Forget (Async) | Eventual consistency OK | Platform Events, Queueable with callout |
| Batch Sync | Large volumes, scheduled | Batch Apex + HttpRequest |
| Event-Driven | React to changes in real time | Change Data Capture, Platform Events |
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.
- 4d ago First seen · 188 lines · 61 tokens per session scan A 636269f31bb2
solution-designer is an agent published in the GitHub repository bhanu91221/sfdx-iq (2 stars, last pushed 3mo ago), licensed MIT. It adds 61 tokens to every session and 1,764 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.