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/madebyaris/rakitui-ai/mcp-tool-structuregit clone --depth 1 https://github.com/madebyaris/rakitui-aiWrote 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/madebyaris/rakitui-ai/mcp-tool-structure)<a href="https://agentmods.dev/rules/madebyaris/rakitui-ai/mcp-tool-structure"><img src="https://agentmods.dev/badge/rules/madebyaris/rakitui-ai/mcp-tool-structure.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.1 | $0.00000 | $0.00224 |
| Opus 5 | $0.00000 | $0.00112 |
| Sonnet 5 | $0.00000 | $0.00045 |
| Haiku 4.5 | $0.00000 | $0.00022 |
Grade A, and why
mcp-tool-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 6d 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 Tool Structure
The project implements an MCP (Model Context Protocol) tool following the framework's required structure.
Key Components
- src/tools/DesignselectionTool.ts: Main tool implementation
- Tool class extends
MCPTool<DesignInput>from MCP framework - Input schema defined using Zod for validation
Tool Implementation Details
- Each tool has a unique
nameproperty ("designselection") - The
descriptionexplains the tool's purpose - The
schemadefines expected input parameters:- design_name_1, design_name_2, design_name_3
- design_html_1, design_html_2, design_html_3
- The
execute()method processes the input and returns a response
MCP Server Setup
- src/index.ts creates and initializes the MCP server
- Tools are exported for the framework to discover
- Server is started with appropriate error handling
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.
- 6d ago First seen · 30 lines · 0 tokens per session scan A e80ec5fe3d68
mcp-tool-structure is a cursor rule published in the GitHub repository madebyaris/rakitui-ai (5 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 224 tokens. 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 cursor rules, from other repositories
typescript-conventions
Label console.warn and console.error calls with their origin.
code-style
TypeScript style, language policy, hygiene, shared domain vocabulary.
angular-typescript-cursorrules-prompt-file
description: "Cursor rules for Angular development with TypeScript integration." globs: / alwaysApply: false.
SmartLead MCP TypeScript Standards
TypeScript coding standards, patterns, and best practices for the SmartLead MCP Server.
typescript
TypeScript coding standards and best practices.
viem
Viem v2 integration patterns and Rules.