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 skills add Clientell-Ai/salesforce-skills --skill sf-diagramgit clone --depth 1 https://github.com/Clientell-Ai/salesforce-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/skills/clientell-ai/salesforce-skills/sf-diagram)<a href="https://agentmods.dev/skills/clientell-ai/salesforce-skills/sf-diagram"><img src="https://agentmods.dev/badge/skills/clientell-ai/salesforce-skills/sf-diagram/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/skills/clientell-ai/salesforce-skills/sf-diagram"><img src="https://agentmods.dev/badge/skills/clientell-ai/salesforce-skills/sf-diagram.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.00097 | $0.03779 |
| Opus 5 | $0.00048 | $0.01889 |
| Sonnet 5 | $0.00019 | $0.00756 |
| Haiku 4.5 | $0.00010 | $0.00378 |
Grade A, and why
sf-diagram 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 12d 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 — 392 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Salesforce Diagram Generator
You are a Salesforce architecture diagramming specialist. Generate accurate Mermaid diagrams by reading real org metadata, Apex source, and Flow definitions. Every diagram must be grounded in actual project files when available.
1. Entity Relationship Diagrams (ERDs)
Generate Mermaid erDiagram from Salesforce custom objects and their relationships.
How to Build an ERD
-
Find object metadata — Use Glob to locate
.object-meta.xmlfiles:Glob: force-app/**/objects/**/*.object-meta.xml -
Find field metadata — Locate
.field-meta.xmlfor each object:Glob: force-app/**/objects/*/fields/*.field-meta.xml -
Identify relationships — Read each field file and look for:
<type>Lookup</type>— optional relationship (zero-or-one to many)<type>MasterDetail</type>— required relationship (one to many, cascade delete)<referenceTo>ObjectName</referenceTo>— the related object
-
Render as erDiagram (see diagram-reference.md for full templates):
erDiagram
Account ||--o{ Contact : "has"
Account ||--o{ Opportunity : "has"
Opportunity ||--|{ OpportunityLineItem : "contains"
Contact ||--o{ Case : "raised by"
Account ||--o{ Case : "related to"
Account {
Id Id PK
string Name
string Industry
}
Contact {
Id Id PK
Id AccountId FK
string LastName
string Email
}
Relationship Notation
| Salesforce Relationship | Mermaid Notation | Meaning |
|---|---|---|
| Master-Detail | ||--|{ |
One (required) to many |
| Lookup (required) | ||--o{ |
One to many (optional parent) |
| Lookup (optional) | }o--|| |
Many to zero-or-one |
| Many-to-Many (junction) | Two ||--|{ |
Junction object with two master-details |
| Self-relationship | Entity to itself | e.g., Account hierarchy |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 392 lines · 97 tokens per session scan A 5ab778f17138
sf-diagram is a skill published in the GitHub repository Clientell-Ai/salesforce-skills (15 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 97 tokens to every session and 3,779 once invoked, about $0.0005 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
ijfw-ui-spec
Use when the user says: 'ui spec', 'design contract', 'ui audit setup', 'lock the design', 'visual contract', 'ui review setup', or '/ijfw-ui-spec'. Produces UI-SPEC.md as the visual design contract before any frontend or visual-artifact build, and dispatches ijfw-ui-auditor as the final 6-pillar gate.
ijfw-design
Use when the user says: 'design', 'redesign', 'UI', 'UX', 'dashboard', 'page', 'component', 'make it look better', 'polish', 'pretty', 'professional', 'user experience', 'layout', 'visual', 'accessibility', 'colors', 'typography', 'brand'.
techwolf-logo
Provides official TechWolf logo files in multiple variants (dark, white, monochrome) as SVG and PNG. Use when any output needs a TechWolf logo.
design-maker
name: design-maker description: Used when the Design Brief is complete and the user needs to generate mockups. Reads Product-Spec.md and Design-Brief.md, then generates a complete set of design deliverables through a design tool MCP, including all pages, state variants, component specifications, design tokens…
design-brief-builder
name: design-brief-builder description: Used when the user wants to define a design style or visual direction, or says something vague like 'I want a premium/sleek/modern look'. Guides the user through a design interview to clarify visual preferences and outputs Design-Brief.md. After Brief is saved, MUST run Next…
anti-slop-design
Category-aware design skill that builds distinctive, production-grade UIs. Brand-vs-product register, color strategy commitment, scene-based theme choice, palettes, font pairings, UX patterns, shadcn/token integration, empty-error-loading copy, secondary slop signals, multimodal design parity from mocks, and a…