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 instructions/taurgis/sfcc-dev-mcp/mcp-node-testsgit 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/instructions/taurgis/sfcc-dev-mcp/mcp-node-tests)<a href="https://agentmods.dev/instructions/taurgis/sfcc-dev-mcp/mcp-node-tests"><img src="https://agentmods.dev/badge/instructions/taurgis/sfcc-dev-mcp/mcp-node-tests.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.00192 | $0.00192 |
| Opus 5 | $0.00096 | $0.00096 |
| Sonnet 5 | $0.00038 | $0.00038 |
| Haiku 4.5 | $0.00019 | $0.00019 |
Grade A, and why
sfcc-dev-mcp mcp-node-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 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.
What it actually says
MCP Programmatic Testing Instructions
For detailed guidance on writing programmatic tests, use the mcp-programmatic-testing skill located at .github/skills/mcp-programmatic-testing/SKILL.md.
Quick Reference
File naming: *.programmatic.test.js
Critical Setup:
beforeEach(() => {
client.clearAllBuffers(); // REQUIRED - prevents test interference
});
Test Execution:
node --test tests/mcp/node/specific-test.programmatic.test.js
npm run test:mcp:node
Critical Rules:
- Never use
Promise.all()with MCP requests - Always include
beforeEachwith buffer clearing - Use
node --test, NOTnpm testfor individual MCP tests
For complete API reference and patterns, see the skill file.
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 · 31 lines · 192 tokens per session scan A 2208b08d8aaf
sfcc-dev-mcp mcp-node-tests.instructions.md is an instructions file published in the GitHub repository taurgis/sfcc-dev-mcp (27 stars, last pushed 4d ago), licensed MIT. It adds 192 tokens to every session, about $0.0010 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 instructions, from other repositories
salesforce-mcp-server CLAUDE.md
Instructions for advancedcommunities/salesforce-mcp-server, covering claude.md, build and development commands, build the typescript project, run development mode with mcp inspector for debugging and build mcp bundle (.mcpb) for distribution.
salesforce-mcp-lib CLAUDE.md
Instructions for Damecek/salesforce-mcp-lib, covering salesforce-mcp-lib development guidelines, active technologies, project structure, commands and code style.
intervals-icu-mcp CLAUDE.md
Instructions for hhopke/intervals-icu-mcp, covering claude.md, project overview, development commands, architecture (quick reference) and tool categories.
flyto-core CLAUDE.md
Instructions for flytohub/flyto-core, covering claude notes, cross-agent handoff and shared code intelligence.
Plonk AGENTS.md
Instructions for ostapondo/Plonk, covering agent rules, layout, adding a module, build & verify and code style.
rosetta AGENTS.md
Instructions for tikoci/rosetta, covering codex instructions for rosetta, first reads, development defaults and mcp and client config.