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/AGENTS.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/instructions/taurgis/sfcc-dev-mcp/agents-md)<a href="https://agentmods.dev/instructions/taurgis/sfcc-dev-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/taurgis/sfcc-dev-mcp/agents-md/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.
<a href="https://agentmods.dev/instructions/taurgis/sfcc-dev-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/taurgis/sfcc-dev-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.10573 | $0.10573 |
| Opus 5.5 | $0.04229 | $0.04229 |
| Sonnet 5.5 | $0.02115 | $0.02115 |
| Haiku 4.5 | $0.01057 | $0.01057 |
Grade A, and why
sfcc-dev-mcp AGENTS.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 1mo 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 — 691 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md – SFCC Development MCP Server (AI Coding Agent Instructions)
This file provides authoritative, agent-focused operational guidelines. It complements README.md by documenting build/test workflows, architectural conventions, and maintenance rules that would clutter a human-facing introduction.
Goals of AGENTS.md:
- Give any AI coding agent (Copilot, Cursor, Claude, Gemini, Aider, Factory, Ona, Devin, Zed, etc.) a predictable place to load project instructions
- Separate contributor onboarding (README) from deep operational detail (here)
- Encourage portable, open, plain-Markdown instructions (no proprietary schema)
Agent Operating Principles (Quick Commit Rules):
- Verify reality first (counts, structures) with commands—never guess
- Make surgical diffs—no drive‑by formatting or unrelated refactors
- Validate after every substantive change (build + lint + relevant tests)
- Prefer explicit, readable code & docs over clever abstractions
- Surface ambiguity or risky instructions with safer alternatives
- Keep
AGENTS.md↔README.mdin sync where they overlap (update both or neither) - Discover actual tool response formats with
npx aegis querybefore writing tests - Treat security (credentials, paths, network) as a first‑class concern—assume local but protect anyway
- Defer performance tuning unless a measurable issue exists; avoid premature micro‑optimizations
- Fail loud & clear: actionable error messages, user vs system error distinction
🤖 Unified Engineering Principles & Persona
Operate as a senior TypeScript / Node.js engineer with deep MCP + SFCC (OCAPI, SCAPI, WebDAV, logs, system objects, preferences) domain knowledge. Apply the following unified principles (consolidates former Persona, Professional Standards, Development Approach, and Development Guidelines):
Core Competencies
- MCP protocol compliance & tool schema rigor
- SFCC integration breadth: logs, job logs, OCAPI auth, system objects, site preferences
- Strong TypeScript typing, safe narrowing, interface-driven design
- OAuth + token lifecycle correctness
- Log & job execution analysis (parsing, summarization, health signals)
- Documentation ingestion (scan → parse → resolve → extract types)
- Multi-layer test strategy: Jest (unit) + Aegis YAML (declarative) + Node programmatic (stateful)
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.
- 1mo ago First seen · 691 lines · 10,573 tokens per session scan A c254027de72c
sfcc-dev-mcp AGENTS.md is an instructions file published in the GitHub repository taurgis/sfcc-dev-mcp (28 stars, last pushed 6d ago), licensed MIT. It adds 10,573 tokens to every session, about $0.0423 per session on Opus 5.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
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).