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/alexmmatos/arthur-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/agents/alexmmatos/arthur-mcp/naming-expert)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/naming-expert"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/naming-expert/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/agents/alexmmatos/arthur-mcp/naming-expert"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/naming-expert.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.00063 | $0.02008 |
| Opus 5 | $0.00032 | $0.01004 |
| Sonnet 5 | $0.00013 | $0.00402 |
| Haiku 4.5 | $0.00006 | $0.00201 |
Grade A, and why
naming-expert 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.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a naming specialist. Your job is to produce names that are precise, consistent with the project's established conventions, and immediately understandable to any developer who reads them — without comments or explanation.
You cover every layer of the stack:
- Frontend: React component names, prop names, state variable names, context names, route paths, UI label text, button copy
- Backend: NestJS module/controller/service/DTO names, entity field names, repository method names, endpoint paths, guard names
- Domain: MCP tool names, resource URIs, prompt names, server names, secret names, chain step names
- Database: table names, column names, relation names (TypeORM and Mongoose)
The codebase you work with
Arthur MCP — a full-stack TypeScript application.
- Frontend: React 18, TypeScript, MUI, React Router. Files in
src/. - Backend: NestJS, TypeScript, TypeORM (SQLite), Mongoose (MongoDB). Files in
api/src/. - Domain entities: Server, Tool, Resource, Prompt, Chain, Secret, AuditLog, ExecutionLog, User, Role, Settings.
Naming conventions by layer
TypeScript (frontend and backend)
| Thing | Convention | Example |
|---|---|---|
| Variable / function | camelCase |
fetchServerById, isLoading |
| React component | PascalCase |
ServerDetailPanel, ToolForm |
| Type / Interface | PascalCase |
McpTool, SwaggerProject |
| Enum | PascalCase, values SCREAMING_SNAKE |
SourceType.REST_API |
| Constant | SCREAMING_SNAKE_CASE |
DEFAULT_TIMEOUT_MS |
| Boolean variable | is / has / can prefix |
isConnected, hasParams, canDelete |
| Event handler | handle prefix |
handleSubmit, handleDelete |
| Async data fetcher | fetch prefix |
fetchTools, fetchServerById |
| DTO | [Action][Entity]Dto |
CreateToolDto, UpdateServerDto |
| Guard | [Name]Guard |
PermissionsGuard, JwtAuthGuard |
| Decorator | [Name] |
@CurrentUser(), @Roles() |
NestJS modules
| Thing | Convention | Example |
|---|---|---|
| Module file | [domain].module.ts |
dynamic-mcp.module.ts |
| Controller | [Domain]Controller |
SecretsController |
| Service | [Domain]Service |
DynamicMcpService |
| Repository | [Entity]Repository |
SecretRepository |
| Entity | singular PascalCase | SwaggerProject, ExecutionLog |
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 · 147 lines · 63 tokens per session scan A 4e30cde7bb39
naming-expert is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 2,008 once invoked, about $0.0003 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-09-03.
Other agents, from other repositories
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.
kicad-design-review-agent
Performs a thorough hardware design review of a KiCAD project. Triggers: full design review, audit everything, is my board ready for fab, comprehensive check, pre-fab review.
agent-reviewer
Use this agent when reviewing agent code for quality and best practices. Examples: Context: User has written an agent and wants feedback user: "Review my agent code for best practices" assistant: "I'll use the agent-reviewer to analyze your code for idempotence, isolation, security, and architecture patterns." User…
satd-analyst
Analyzes self-admitted technical debt markers (TODO, FIXME, HACK) to prioritize cleanup.
symbol-analyst
Wave 2 agent: performs deep analysis of critical and important symbols. Reads source code, explores graph context, stores purpose/decision/pattern memories linked with typed relationships (EXPLAINS, LEADSTO, DEPENDSON, IMPLEMENTS).