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.
git clone --depth 1 https://github.com/commercetools/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/rules/commercetools/commerce-mcp/project-structure)<a href="https://agentmods.dev/rules/commercetools/commerce-mcp/project-structure"><img src="https://agentmods.dev/badge/rules/commercetools/commerce-mcp/project-structure/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/rules/commercetools/commerce-mcp/project-structure"><img src="https://agentmods.dev/badge/rules/commercetools/commerce-mcp/project-structure.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.00002 | $0.01555 |
| Opus 5.5 | $0.00001 | $0.00622 |
| Sonnet 5.5 | $0.00000 | $0.00311 |
| Haiku 4.5 | $0.00000 | $0.00155 |
Grade A, and why
project-structure 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.
This is a copy
100% identical to project-structure — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Structure
This document provides an overview of the directory structure for this repository.
/
├── .github/ # GitHub specific configurations
│ ├── ISSUE_TEMPLATE/ # Templates for creating GitHub issues
│ │ ├── bug_report.yml # Template for bug reports
│ │ ├── config.yml # Configuration for issue templates
│ │ └── feature_request.yml # Template for feature requests
│ └── workflows/ # GitHub Actions workflows
│ ├── main.yml # Main CI/CD workflow (e.g., testing, linting)
│ └── release.yml # Workflow for creating releases
├── .git/ # Git version control data (usually hidden)
├── .vscode/ # VS Code editor configurations
├── modelcontextprotocol/ # Core package for the Model Context Protocol implementation
│ ├── node_modules/ # Project dependencies (managed by npm/pnpm/yarn)
│ ├── scripts/ # Utility scripts for the package
│ │ └── publish # Script for publishing the package
│ ├── src/ # Source code for the modelcontextprotocol package
│ │ ├── index.ts # Main entry point for the package
│ │ └── test/ # Unit tests for the package
│ │ └── index.test.ts # Tests for the main entry point
│ ├── .gitignore # Specifies intentionally untracked files that Git should ignore
│ ├── .prettierrc # Configuration file for the Prettier code formatter
│ ├── eslint.config.mjs # Configuration file for the ESLint linter
│ ├── jest.config.ts # Configuration file for the Jest testing framework
│ ├── package-lock.json # Records exact versions of dependencies (npm)
│ ├── package.json # Defines package metadata, dependencies, and scripts
│ ├── pnpm-lock.yaml # Records exact versions of dependencies (pnpm)
│ ├── README.md # README specific to the modelcontextprotocol package
│ └── tsconfig.json # TypeScript compiler options for this package
├── typescript/ # TypeScript specific implementations or toolkits using the protocol
│ ├── examples/ # Example usage of the TypeScript toolkit
│ │ ├── ai-sdk/ # Example using the AI SDK integration
│ │ │ ├── .env.template # Template for environment variables
│ │ │ ├── index.ts # Example script demonstrating usage
│ │ │ ├── package.json # Dependencies for the example
│ │ │ ├── README.md # README for the ai-sdk example
│ │ │ └── tsconfig.json # TypeScript configuration for the example
│ │ └── langchain/ # Example using the Langchain integration
│ │ ├── .env.template # Template for environment variables
│ │ ├── index.ts # Example script demonstrating usage
│ │ ├── package.json # Dependencies for the example
│ │ ├── README.md # README for the langchain example
│ │ └── tsconfig.json # TypeScript configuration for the example
│ ├── node_modules/ # Project dependencies (managed by npm/pnpm/yarn)
│ ├── scripts/ # Utility scripts for the TypeScript packages/workspace
│ │ └── publish # Script for publishing the package(s)
│ ├── src/ # Source code for the TypeScript toolkit/packages
│ │ ├── ai-sdk/ # Integration layer for the AI SDK
│ │ │ ├── index.ts # Entry point for the AI SDK integration
│ │ │ └── toolkit.ts # Toolkit implementation specific to AI SDK
│ │ ├── langchain/ # Integration layer for Langchain
│ │ │ ├── index.ts # Entry point for the Langchain integration
│ │ │ └── toolkit.ts # Toolkit implementation specific to Langchain
│ │ ├── modelcontextprotocol/# Re-export or specific implementation related to the core protocol
│ │ │ ├── index.ts # Entry point
│ │ │ └── toolkit.ts # Toolkit implementation
│ │ ├── shared/ # Shared utilities and components for TypeScript packages
│ │ │ ├── api.ts # API definitions or clients
│ │ │ ├── configuration.ts # Configuration handling logic
│ │ │ ├── functions.ts # Utility functions
│ │ │ ├── parameters.ts # Parameter definitions or handling
│ │ │ ├── prompts.ts # Prompt templates or management
│ │ │ └── tools.ts # Tool definitions or handling
│ │ └── test/ # Tests for the TypeScript code
│ │ └── shared/ # Tests for the shared components
│ │ ├── configuration.test.ts # Tests for configuration logic
│ │ └── functions.test.ts # Tests for utility functions
│ ├── .gitignore # Specifies intentionally untracked files that Git should ignore
│ ├── .prettierrc # Configuration file for the Prettier code formatter
│ ├── .vscode/ # VS Code editor configurations specific to the typescript directory
│ ├── eslint.config.mjs # Configuration file for the ESLint linter
│ ├── jest.config.ts # Configuration file for the Jest testing framework
│ ├── package-lock.json # Records exact versions of dependencies (npm)
│ ├── package.json # Defines package metadata, dependencies, and scripts (likely for the workspace)
│ ├── pnpm-lock.yaml # Records exact versions of dependencies (pnpm)
│ ├── pnpm-workspace.yaml # Defines the pnpm workspace configuration
│ ├── README.md # README specific to the TypeScript part of the repository
│ ├── template.env # Template for environment variables
│ ├── tsconfig.json # Base TypeScript compiler options for the workspace
│ └── tsup.config.ts # Configuration for the tsup bundler
├── .gitignore # Specifies intentionally untracked files that Git should ignore at the root level
├── LICENSE # Repository license information
├── package-lock.json # Records exact versions of root-level dependencies (if any, potentially for dev tools)
├── package.json # Root package.json, might define workspace root or global dev dependencies
├── README.md # Main README file for the repository
└── SECURITY.md # Security policy and reporting instructions
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 · 96 lines · 2 tokens per session scan A 5f8f2bfc69dc
project-structure is a cursor rule published in the GitHub repository commercetools/commerce-mcp (4 stars, last pushed 2d ago), licensed MIT. It adds 2 tokens to every session and 1,555 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to project-structure, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).