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 skills/divingsbysangam/salesforce-compound-engineering-plugin/graphql-patternsnpx skills add divingsbysangam/salesforce-compound-engineering-plugin --skill graphql-patternsgit clone --depth 1 https://github.com/divingsbysangam/salesforce-compound-engineering-pluginWrote 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/divingsbysangam/salesforce-compound-engineering-plugin/graphql-patterns)<a href="https://agentmods.dev/skills/divingsbysangam/salesforce-compound-engineering-plugin/graphql-patterns"><img src="https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/graphql-patterns.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.00040 | $0.00497 |
| Opus 5 | $0.00020 | $0.00249 |
| Sonnet 5 | $0.00008 | $0.00099 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
graphql-patterns 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 — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GraphQL Patterns for LWC
SCOPE: LWC_ONLY — This skill applies to Lightning Web Components that talk to the Salesforce UI API via GraphQL (lightning/uiGraphQLApi and lightning/graphql). For pure Apex data access, use apex-patterns. For component-level state/comm patterns, use lwc-patterns. For integration with external GraphQL servers, use integration-patterns.
Required reads
Procedure lives in sibling files, not only in this orchestrator:
- Decision: GraphQL vs Apex vs uiRecordApi — read
references/decision-graphql-vs-apex-vs-uirecordapi.mdbefore acting on this section. - Permission model — the metadata gotcha (READ THIS) — read
references/permission-model-the-metadata-gotcha-read-this.mdbefore acting on this section. - Module choice — read
references/module-choice.mdbefore acting on this section. - Query basics — read
references/query-basics.mdbefore acting on this section. - Variables (reactive parameters) — read
references/variables-reactive-parameters.mdbefore acting on this section. - Nested relationships (the killer feature) — read
references/nested-relationships-the-killer-feature.mdbefore acting on this section. - Mutations (Create / Update / Delete) — read
references/mutations-create-update-delete.mdbefore acting on this section. - Refresh patterns — read
references/refresh-patterns.mdbefore acting on this section. - Error handling — read
references/error-handling.mdbefore acting on this section. - Security: GraphQL string escaping — read
references/security-graphql-string-escaping.mdbefore acting on this section. - Composition pattern (multiple components sharing LDS) — read
references/composition-pattern-multiple-components-sharing-lds.mdbefore acting on this section. - Working reference — read
references/working-reference.mdbefore acting on this section. - Common pitfalls — read
references/common-pitfalls.mdbefore acting on this section.
What ships with it
13 files 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.
- references/common-pitfalls.md 1.0 KB
- references/composition-pattern-multiple-components-sharing-lds.md 618 B
- references/decision-graphql-vs-apex-vs-uirecordapi.md 2.3 KB
- references/error-handling.md 1.1 KB
- references/module-choice.md 579 B
- references/mutations-create-update-delete.md 2.0 KB
- references/nested-relationships-the-killer-feature.md 1.8 KB
- references/permission-model-the-metadata-gotcha-read-this.md 2.2 KB
- references/query-basics.md 1.8 KB
- references/refresh-patterns.md 752 B
- references/security-graphql-string-escaping.md 881 B
- references/variables-reactive-parameters.md 794 B
- references/working-reference.md 542 B
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 · 30 lines · 40 tokens per session scan A 239ad037c9c0
graphql-patterns is a skill published in the GitHub repository divingsbysangam/salesforce-compound-engineering-plugin (10 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 497 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…