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/kaminari-ad/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/kaminari-ad/mcp/mcp-naming-conventions)<a href="https://agentmods.dev/rules/kaminari-ad/mcp/mcp-naming-conventions"><img src="https://agentmods.dev/badge/rules/kaminari-ad/mcp/mcp-naming-conventions/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/kaminari-ad/mcp/mcp-naming-conventions"><img src="https://agentmods.dev/badge/rules/kaminari-ad/mcp/mcp-naming-conventions.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.00000 | $0.01207 |
| Opus 5.5 | $0.00000 | $0.00483 |
| Sonnet 5.5 | $0.00000 | $0.00241 |
| Haiku 4.5 | $0.00000 | $0.00121 |
Grade A, and why
mcp-naming-conventions 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 today.
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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Naming Conventions — mcp/ (TypeScript)
File names — kebab-case, suffixed by role
| Role | Filename pattern | Example |
|---|---|---|
| Tool | <name>.tool.ts |
list-scans.tool.ts |
| Port (interface) | <concept>.ts |
api-gateway.ts |
| Adapter | <tech>-<concept>.ts |
http-api-gateway.ts |
| Value object | <concept>.ts |
bearer-token.ts |
| Domain service | <concept>-<role>.ts |
session-binding-policy.ts |
| Bootstrap | <transport>-bootstrap.ts |
stdio-bootstrap.ts |
| Middleware | <concept>-middleware.ts |
auth-middleware.ts |
| Test (mirror src) | <file>.test.ts |
list-scans.tool.test.ts |
| Fake (in tests/) | fake-<port>.ts |
fake-api-gateway.ts |
mcp/scripts/check-tool-naming.ts enforces tool naming.
Symbol names
| Kind | Convention | Example |
|---|---|---|
| Tool const | <camelCase>Tool (matches filename) |
listScansTool |
Tool name literal |
<snake_case> (matches filename) |
"list_scans" |
| Interface | PascalCase, no I prefix |
ApiGateway |
| Type alias | PascalCase | ToolError |
| Concrete class | PascalCase with role suffix | HttpApiGateway |
| Function | camelCase verb phrase | createPinoLogger |
| Const | camelCase, UPPER_SNAKE for true constants only |
defaultRateLimitRpm / LINE_LIMIT |
| Enum-like union | as const object, PascalCase keys |
ToolStatus.Success |
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.
- today First seen · 89 lines · 0 tokens per session scan A 62649f50ea71
mcp-naming-conventions is a cursor rule published in the GitHub repository kaminari-ad/mcp (0 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,207 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-11-05.
Other cursor rules, from other repositories
typescript
Rules for when building Javascript and/or Typescript projects.
commander
When using the commander.js NPM library.
010-python-tooling
Python tooling and dependency conventions for plugin-eval and tools/.
chrome-extension-dev-js-typescript-cursorrules-pro
Cursor rules for VSCode extension development with Electron and TypeScript integration.
javascript-typescript-code-quality-cursorrules-pro
Cursor rules for JavaScript and TypeScript development with code quality integration.
ai-agent-specialist
Cursor rules for TypeScript, React, Node.js, clean architecture, testing, and WHY-oriented engineering guidance.