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/ameghcoder/e-commerce-mcp/claude-mdgit clone --depth 1 https://github.com/ameghcoder/e-commerce-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/ameghcoder/e-commerce-mcp/claude-md)<a href="https://agentmods.dev/instructions/ameghcoder/e-commerce-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/ameghcoder/e-commerce-mcp/claude-md.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.01132 | $0.01132 |
| Opus 5 | $0.00566 | $0.00566 |
| Sonnet 5 | $0.00226 | $0.00226 |
| Haiku 4.5 | $0.00113 | $0.00113 |
Grade A, and why
e-commerce-mcp CLAUDE.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 3d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — commerce-ops-mcp
This project opts out of the reviewer-first default: Claude is expected to implement directly here, within the scope rules below.
Project purpose
This is a take-home engineering assignment: an AI-first commerce operations challenge. The final solution is a remotely hosted MCP server, written in TypeScript, that lets an AI agent investigate commerce problems on behalf of an operations specialist.
Confirmed scope
The client has confirmed the product scope. This is no longer a hypothesis:
A single focused end-to-end workflow is the right level of scope. Separate coverage of all four commerce domains (orders, payments, inventory, fulfillment) as independent workflows is explicitly out of scope.
The chosen workflow is delayed-order investigation: given an order, an operations specialist (via an AI agent) asks "why is this order delayed, and what should I do about it?", and the MCP provides the evidence, diagnosis, and recommended resolution to answer that.
Order, payment, inventory, and fulfillment data all remain relevant — but strictly as supporting evidence for this one workflow, never as independent domains with their own tools or CRUD surface. Think "delayed-order investigation MCP," not "orders MCP + payments MCP + inventory MCP + fulfillment MCP."
Scope rule
Do not implement separate workflows or tool surfaces for:
- payments (beyond what's needed to explain a delay)
- inventory (beyond what's needed to explain a delay)
- fulfillment (beyond what's needed to explain a delay)
- generic/full order management (search and read for investigation only — not creation, editing, or lifecycle management of orders)
If a feature would only make sense as its own domain workflow (e.g., "list all payment failures across all orders" as a payments-ops feature, unrelated to investigating one delayed order), it is out of scope. Name it as a possible future extension instead of building it.
Current stage
The domain/data foundation and the MCP server are both done, over two
transports: src/mcp/server.ts (stdio, local) and src/mcp/http.ts
(Streamable HTTP, stateless, remote — deployed to Render). Both share tool
registration from src/mcp/create-server.ts, so the four tools are
identical regardless of transport.
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.
- 3d ago First seen · 124 lines · 1,132 tokens per session scan A ec2eee48e2da
e-commerce-mcp CLAUDE.md is an instructions file published in the GitHub repository ameghcoder/e-commerce-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 1,132 tokens to every session, about $0.0057 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 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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.