Borrowing it
Nothing to install: this file belongs to taurgis/sfcc-dev-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/taurgis/sfcc-dev-mcp/main/.github/skills/mcp-development/SKILL.mdgit clone --depth 1 https://github.com/taurgis/sfcc-dev-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/taurgis/sfcc-dev-mcp/mcp-development)<a href="https://agentmods.dev/skills/taurgis/sfcc-dev-mcp/mcp-development"><img src="https://agentmods.dev/badge/skills/taurgis/sfcc-dev-mcp/mcp-development.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.00049 | $0.02758 |
| Opus 5 | $0.00024 | $0.01379 |
| Sonnet 5 | $0.00010 | $0.00552 |
| Haiku 4.5 | $0.00005 | $0.00276 |
Grade A, and why
mcp-development 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 6d 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 — 402 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Development Skill
Always load this skill before designing, implementing, reviewing, auditing, or hardening TypeScript MCP servers.
Protocol Target
- Target MCP protocol revision:
2025-11-25. - If you must support legacy clients, document exact compatibility with
2024-11-05HTTP+SSE behavior. - Treat protocol version negotiation as mandatory, not optional.
When to Use
- Building a new MCP server from scratch
- Choosing between STDIO and Streamable HTTP transport
- Designing tools, resources, and prompts with strict schemas
- Hardening security for multi-tenant or networked deployments
- Setting up testing, CI/CD, and production operations
- Reviewing an existing MCP server for protocol correctness and resilience
When NOT to Use
- Simple one-off scripts with no MCP protocol surface
- Frontend-only tasks unrelated to MCP integration
- Generic REST API design without MCP-specific concerns
SDK Version Guardrails
- Be explicit about TypeScript SDK generation in docs and examples.
- Current official guidance indicates v2 is still evolving; validate stability expectations before production rollout.
- If you adopt v2 package split, ensure examples use the correct package names for server, client, and runtime transports.
- Do not assume server-side SSE transport support in new SDK major versions; confirm with the current migration docs.
Architecture First
Treat MCP as three actors:
- Host: the user-facing AI application
- Client: host-side protocol manager for one server connection
- Server: your TypeScript process exposing tools/resources/prompts
Separate two layers:
- Data layer: JSON-RPC 2.0 semantics and MCP capability lifecycle
- Transport layer: how bytes move (STDIO or Streamable HTTP)
Transport Decision Matrix
| Vector | STDIO | Streamable HTTP |
|---|---|---|
| Runtime model | Child process per client | Independent network service |
| Concurrency | Single client per process | Multi-client and multiplexed |
| Latency | Very low local latency | Network and TLS overhead |
| Auth complexity | Local trust boundary | OAuth/token/TLS required |
| Best fit | Local IDE, desktop workflows | Shared services, SaaS, multi-tenant |
What ships with it
7 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/logging-progress-cancellation.md 2.9 KB
- references/protocol-versioning-and-negotiation.md 2.8 KB
- references/security-authorization-oauth.md 3.2 KB
- references/tasks-experimental.md 4.5 KB
- references/tools-resources-prompts-data-shapes.md 6.5 KB
- references/transports-stdio-vs-streamable-http.md 4.0 KB
- references/typescript-sdk-v1-v2-notes.md 2.7 KB
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.
- 6d ago First seen · 402 lines · 49 tokens per session scan A 49fa6fd0c198
mcp-development is a skill published in the GitHub repository taurgis/sfcc-dev-mcp (27 stars, last pushed 7d ago), licensed MIT. It adds 49 tokens to every session and 2,758 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-30.
Other skills, from other repositories
nebula-logger-instrumentation
Use this skill when the user wants to add or update Nebula Logger instrumentation in Apex, LWC, Aura, Flow, or OmniStudio. Covers logging APIs, save patterns, record association, scenarios, tags, async transaction linking, and save method selection.
nebula-logger-plugin-development
Use this skill when the user wants to build a new plugin that extends Nebula Logger - for example, custom trigger handlers on LogEntryEvente / Logc / LogEntryc, custom purge actions, or Slack-style outbound integrations. Covers the plugin framework interfaces, LoggerPluginmdt configuration, package layout, and testing…
nebula-logger-testing-your-code
Use this skill when the user wants to write Apex or LWC tests for code that calls Nebula Logger. Covers observing that the right entries were buffered, controlling logging levels inside tests, isolating tests from persisted Logc / LogEntryc / LogEntryTagc / LoggerScenarioc / LoggerTagc records, and Nebula Logger APIs…
nebula-logger-purging-and-retention
Use this skill when the user wants to configure how long Nebula Logger keeps log records before deleting or archiving them. Covers retention date semantics on Logc, the LogBatchPurger batch job, LogBatchPurgeScheduler, purge action values, and how to tune retention per user, profile, or scenario.
nebula-logger-install
Use this skill when the user wants to install and configure Nebula Logger in a Salesforce org for the first time. Covers package selection, installation paths, permissions, LoggerSettingsc hierarchy, and first-run troubleshooting.
nebula-logger-best-practices
Use this skill when the user wants to review, harden, or standardize Nebula Logger usage across a Salesforce team. Covers operational logging standards, environment-aware settings, limit-aware design, and governance guardrails.