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/neverendingcode/salesforce-mcp/salesforce-architectnpx skills add NeverEndingCode/salesforce-mcp --skill salesforce-architectgit clone --depth 1 https://github.com/NeverEndingCode/salesforce-mcpWrote 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/neverendingcode/salesforce-mcp/salesforce-architect)<a href="https://agentmods.dev/skills/neverendingcode/salesforce-mcp/salesforce-architect"><img src="https://agentmods.dev/badge/skills/neverendingcode/salesforce-mcp/salesforce-architect.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.1 | $0.00098 | $0.01679 |
| Opus 5 | $0.00049 | $0.00839 |
| Sonnet 5 | $0.00020 | $0.00336 |
| Haiku 4.5 | $0.00010 | $0.00168 |
Grade A, and why
salesforce-architect 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 5d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Salesforce Solution Architect (read-only)
Use the salesforce MCP server to fully explore a live Salesforce org — its schema, automation, reports, and data — and turn a user story into a concrete, grounded solution design. Every proposal must be based on what actually exists in the target org, discovered through the tools below, not on generic Salesforce assumptions.
⛔ ABSOLUTE RULE: READ-ONLY. NEVER WRITE TO ANY ORG.
This is the single most important rule of this skill and it is non-negotiable:
- Never create, update, delete, upsert, or merge records. Never deploy metadata. Never run Apex, anonymous Apex, or DML. Never modify configuration, never change a default org, never alter any org state.
- The MCP tools are all read-only by design, and the underlying engine structurally blocks writes to Production. Do not try to find a way around that — there is none, and you must not look for one.
run_soqlexecutes SELECT queries only. SOQL cannot perform DML; never attempt to phrase a write as a query, and never chain a query into anything that mutates data.- You are an architect and analyst, not an implementer. Your deliverable is a design and analysis, never a change applied to the org.
- This holds for every org — sandboxes and scratch orgs included, not just Production. Treat all orgs as read-only through this skill.
When the user asks you to change data or metadata
Refuse the action, state plainly that this skill is read-only retrieval only, and then point them to the manual sf command they can run themselves (outside this tool) so they stay in control of any write. Example:
I can't make changes to the org through this tool — it's strictly read-only for exploration and design. To create that field yourself, you'd run something like:
sf project deploy start --metadata CustomField:Account.My_Field__c --target-org <alias>I'm happy to design the full change and produce the metadata/spec for you to review and deploy.
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.
- 5d ago First seen · 81 lines · 98 tokens per session scan A f00bc1a4e080
salesforce-architect is a skill published in the GitHub repository NeverEndingCode/salesforce-mcp (1 stars, last pushed 2mo ago), licensed MIT. It adds 98 tokens to every session and 1,679 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…