sfcc-dev-mcp: Instructions file for GitHub Copilot

.github/instructions/mcp-yml-tests.instructions.md

sfcc-dev-mcp mcp-yml-tests.instructions.md is an instructions file for GitHub Copilot from taurgis/sfcc-dev-mcp. It costs 212 tokens per session, scanned A, original, MIT.

Instructions for testing MCP servers with YAML files. MCP, the Model Context Protocol, lets an agent call tools provided by another program or service.

In plain words
What is it for?
Use it to create and run documentation-only or full YAML tests, check values and types, and match parts of tool responses.
Why use it?
It shows how to discover a tool’s real response format before writing tests, reducing tests that fail because they expect the wrong data shape.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is taurgis/sfcc-dev-mcp's own configuration. It tells GitHub Copilot how to work on sfcc-dev-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything sfcc-dev-mcp configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/taurgis/sfcc-dev-mcp/main/.github/instructions/mcp-yml-tests.instructions.md
Clone the repo
git clone --depth 1 https://github.com/taurgis/sfcc-dev-mcp

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for sfcc-dev-mcp mcp-yml-tests.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/taurgis/sfcc-dev-mcp/mcp-yml-tests/github.svg)](https://agentmods.dev/instructions/taurgis/sfcc-dev-mcp/mcp-yml-tests)
Your own site
<a href="https://agentmods.dev/instructions/taurgis/sfcc-dev-mcp/mcp-yml-tests"><img src="https://agentmods.dev/badge/instructions/taurgis/sfcc-dev-mcp/mcp-yml-tests/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.

agentmods 80×15 button for sfcc-dev-mcp mcp-yml-tests.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/taurgis/sfcc-dev-mcp/mcp-yml-tests"><img src="https://agentmods.dev/badge/instructions/taurgis/sfcc-dev-mcp/mcp-yml-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 212 This file is loaded in full into every session.
When invoked 212 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00212 $0.00212
Opus 5 $0.00106 $0.00106
Sonnet 5 $0.00042 $0.00042
Haiku 4.5 $0.00021 $0.00021

Measured 9d ago against content hash b439fc588c08, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

sfcc-dev-mcp mcp-yml-tests.instructions.md 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 9d 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.

.github/instructions/mcp-yml-tests.instructions.md · 27 lines

What it actually says

MCP YAML Testing Instructions

For detailed guidance on writing YAML tests, use the mcp-yaml-testing skill located at .github/skills/mcp-yaml-testing/SKILL.md.

Quick Reference

Golden Rule: Always discover response formats first:

npx aegis query [tool_name] '[params]' --config ./aegis.config.docs-only.json

Test Execution:

npm run test:mcp:yaml        # docs-only mode
npm run test:mcp:yaml:full   # full mode with credentials

Common Patterns:

  • "match:contains:substring" - Contains text
  • "match:regex:\\d+" - Regex (double-escape backslashes)
  • "match:type:array" - Type validation
  • "match:arrayElements:" with "match:partial:" - Flexible array validation

For complete pattern reference and troubleshooting, see the skill file.

Changes

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.

  1. 9d ago First seen · 27 lines · 212 tokens per session scan A b439fc588c08

Subscribe to this mod's changes

sfcc-dev-mcp mcp-yml-tests.instructions.md is an instructions file published in the GitHub repository taurgis/sfcc-dev-mcp (28 stars, last pushed 2d ago), licensed MIT. It adds 212 tokens to every session, about $0.0011 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.

Related

Other instructions, from other repositories

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens