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 rules/commercetools/mcp-essentials/extending-function-paramsgit clone --depth 1 https://github.com/commercetools/mcp-essentialsWhat 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.00012 | $0.00600 |
| Opus 5 | $0.00006 | $0.00300 |
| Sonnet 5 | $0.00002 | $0.00120 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
extending-function-params 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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- extending-function-params — 100% identical, 0 lines differ
What it actually says
Always follow these steps in order:
-
Parameter Schema Update:
- Locate the parameters file (usually
typescript/src/shared/(namespace)/parameters.ts) - Add new parameters to the Zod schema
- For each parameter:
- Define the correct type (e.g., z.number(), z.array(z.string()))
- Add appropriate validations (e.g., .min(), .max())
- Mark as .optional() if not required
- Add .describe() with clear documentation
- Include examples in the description for complex types
- Locate the parameters file (usually
-
Function Implementation Update:
- Locate the function file (usually
typescript/src/shared/(namespace)/functions.ts) - Add new parameters to the queryArgs object
- Use spread operator with null checks for optional params
- Format:
...(params.newParam && {newParam: params.newParam}) - Remove any outdated comments
- Locate the function file (usually
-
Documentation Update:
- Locate the prompts file (usually named
typescript/src/shared/(namespace)/prompts.ts) - Update the function's prompt string
- For each parameter add:
- Parameter name
- Type information
- Optional/required status
- Default value if any
- Valid range if applicable
- Example usage for complex types
- Locate the prompts file (usually named
-
Test Coverage Update:
- Locate the test file (usually
typescript/src/shared/(namespace)/test/functions.test.ts) - Add/update test cases:
- Test with default parameters
- Test with all new parameters
- Test error scenarios
- Verify all parameters are correctly passed to the API
- Ensure proper mock setup and assertions
- Locate the test file (usually
-
Verification:
- Ensure all files are consistent with each other
- Parameter types match between schema and tests
- Examples in prompts match test cases
- All optional parameters handle undefined cases
- Error handling is properly tested
Example: When adding 'offset' parameter:
-
In parameters.ts:
offset: z .number() .int() .min(0) .optional() .describe('The number of items to skip before starting to collect the result set.') -
In functions.ts:
queryArgs: { ...(params.offset && {offset: params.offset}), } -
In prompts.ts:
- offset (int, optional): The number of items to skip before starting to collect the result set. -
In functions.test.ts:
it('should list products with all query parameters', async () => { const params = { offset: 40, // other params... }; // test implementation });
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.
- yesterday First seen · 87 lines · 600 tokens per session scan A 3c7de024b27d
extending-function-params is a cursor rule published in the GitHub repository commercetools/mcp-essentials (13 stars, last pushed 15d ago), licensed MIT. It adds 12 tokens to every session and 600 once invoked, about $0.0001 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 cursor rules, from other repositories
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.